Issue metadata
Sign in to add a comment
|
Service workers: "Bypass for network" is not working for initial document load
Reported by
ultco...@gmail.com,
Oct 14 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Set up a localhost server with an `index.html` file 2. Register a service worker with a `fetch` event that responds to `index.html` requests 3. Open DevTools -> Application -> Service Workers and tick the "Bypass for network" option 4. Reload the localhost index.html page What is the expected behavior? The `index.html` response should be fetched from the network. What went wrong? The `index.html` response comes from the registered service worker. (other resources referenced from the index.html are fetched from the network as expected) Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: OS X 10.12.5 Flash Version:
,
Oct 16 2017
,
Oct 17 2017
ultcombo@ Thanks for the issue. Can you please provide us the index.html file which will help us in further triaging of this issue. Thanks...
,
Oct 22 2017
Hello, I've added a zip file containing a minimum reproducible test case with the index.html and service worker code. You can run it with any local HTTP server (e.g. `python -m SimpleHTTPServer`).
,
Oct 22 2017
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 23 2017
@horo: mind taking a look?
,
Oct 24 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ultco...@gmail.com
, Oct 14 2017