| commit | 5febe1427ee8a7c5a0c6feb1ee3f69e2c93f57a4 | |
| author | falken <falken@chromium.org> | |
| Fri, 8 May 2015 10:28:08 +0000 (8 03:28 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 8 May 2015 10:28:38 +0000 (8 10:28 +0000) | ||
| tree | e3cae022c691fa9d908edbc38d374101f595f22f | treesnapshot (tar.gz zip) |
| parent | 2c7f34a4d97b466b25bb67eb0145036dcede6053 | commitdiff |
Service Worker: Fallback to network when SW interception unexpectedly fails.
Failing to dispatch the fetch event is an exceptional case: the SW may
be unexpectedly missing or it failed to start up, etc. For a main resource
load, responding with error just blocks access to the page, so try to
fallback to network in that case. For a subresource load, it'd be strange
for some subresources to come from the SW and some from the network, so
return error as currently implemented.
BUG=448003
Review URL: https://codereview.chromium.org/1134483003
Cr-Commit-Position: refs/heads/master@{#328942}
Failing to dispatch the fetch event is an exceptional case: the SW may
be unexpectedly missing or it failed to start up, etc. For a main resource
load, responding with error just blocks access to the page, so try to
fallback to network in that case. For a subresource load, it'd be strange
for some subresources to come from the SW and some from the network, so
return error as currently implemented.
BUG=448003
Review URL: https://codereview.chromium.org/1134483003
Cr-Commit-Position: refs/heads/master@{#328942}