New issue
Advanced search Search tips

Issue 761963 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Long waiting for service worker times with query param

Reported by ahoj...@gmail.com, Sep 5 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3205.0 Safari/537.36

Steps to reproduce the problem:
1. Go into https://www.forbes.pl
2. wait to activate service worker and reload the page with additional querystring
3. on the main thret there should be a long time "waiting for service worker"

What is the expected behavior?
waiting for service worker should be wery short

What went wrong?
there was a long time waiting for service worker

Did this work before? No 

Chrome version: 63.0.3205.0  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

none
 

Comment 1 by math...@qiwi.be, Sep 5 2017

Owner: paulir...@chromium.org
Status: Untriaged (was: Unconfirmed)
Paul, could you take a look please?

Comment 2 by ahoj...@gmail.com, Sep 5 2017

Zrzut ekranu 2017-09-05 o 12.43.32.png
128 KB View Download
Components: -Platform>DevTools Blink>ServiceWorker
Labels: -OS-Mac
Owner: ----
Summary: Long waiting for service worker times with query param (was: Senior software developer)
Wow very interesting. 


My repro:

1. Go to https://www.forbes.pl/
2. Wait for page to load
3. In DevTools application panel > Service Workers, confirm the worker is "activated and running"
4. Change the url to add a query param, such as https://www.forbes.pl/?aa
5. Look at the network panel for the main resource

2 second long "Request to service worker". :o



Screen Shot 2017-09-11 at 2.23.33 PM.png
666 KB View Download
Screen Shot 2017-09-11 at 2.23.57 PM.png
131 KB View Download

Comment 4 by horo@chromium.org, Sep 11 2017

Status: WontFix (was: Untriaged)
I think it is because it takes time for the service worker to receive the HTTP response from the server.
You can see the request from the SW when you enable the "Preserve log" check box. 
forbes.png
392 KB View Download
Ah yes, and any new query string is treated as a brand new resource by the browser, so it'd never use the cached one.

Sounds good to me.

Sign in to add a comment