summaryrefslogtreecommitdiffstats
path: root/content/browser/mojo
diff options
context:
space:
mode:
authorjungkee.song <jungkee.song@samsung.com>2016-01-26 02:03:32 -0800
committerCommit bot <commit-bot@chromium.org>2016-01-26 10:05:05 +0000
commit2c7aaaf09eab313a07c425c474256f92957da931 (patch)
tree9a8ea0388363e5c40416b27a8ed84570b603eb1a /content/browser/mojo
parent400c9af5cce40f11a2bfa61b7cbc21fb29e6ea63 (diff)
downloadchromium_src-2c7aaaf09eab313a07c425c474256f92957da931.zip
chromium_src-2c7aaaf09eab313a07c425c474256f92957da931.tar.gz
chromium_src-2c7aaaf09eab313a07c425c474256f92957da931.tar.bz2
Service Worker: Change the criteria for bumping the last update check time
As per the latest spec change, when an update successfully loaded a script resource from the network (having bypassed the HTTP cache), the registration's last update check time should be updated regardless of whether the installation of the fetched resource succeeds or fails. While the existing code updates the time stamp only when the subsequent installation of the newly received script is successfully completed (or the loaded script is byte-for-byte match to the incumbent script resource), this CL makes it bump the time stamp as soon as the update succeeded. This CL added a condition for checking whether the script resource was served from the network: if (net_request_->response_info().network_accessed && !(net_request_->response_info().was_cached)) // This line is added. Spec discussion: https://github.com/slightlyoff/ServiceWorker/issues/514#issuecomment-135641718 BUG=539709 Review URL: https://codereview.chromium.org/1381153004 Cr-Commit-Position: refs/heads/master@{#371485}
Diffstat (limited to 'content/browser/mojo')
0 files changed, 0 insertions, 0 deletions