UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0
Steps to reproduce the problem:
1. Go to https://gdgnd-devfest16.firebaseapp.com/
2. Reload page after it's been loaded
What is the expected behavior?
The page should fail to load when reloaded after the service worker is installed and controlling the page.
What went wrong?
The service worker on the page has a bug per the spec and should fail to load:
1) The page pre-cache install is caching /index.html which redirects to /.
2) In the fetch even the top level page is normalized back to index.html and looks this response up in the Cache API.
3) Returning a redirected Response to a navigation with redirect mode manual is illegal per the spec.
Step 3 results in a failure in firefox, but chrome accepts it. This is against the spec.
See HTTP Fetch step 3.3.3:
https://fetch.spec.whatwg.org/#http-fetch
Did this work before? No
Does this work in other browsers? Yes
Chrome version: 56.0.2896.0 (Official Build) canary (64-bit) Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0
It may be that this check for redirected Response objects may just not have been implemented yet. Its also possible that the Cache API in chrome is incorrectly losing the redirected status of the Response.
Comment 1 by horo@chromium.org
, Oct 24 2016