Limited to 6 concurrent ServiceWorker FetchEvents when using HTTP/1
Reported by
zbbjorn...@gmail.com,
Apr 20 2018
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: Send >6 requests that are within a ServiceWorker's scope and observe how many concurrent requests are allowed. What is the expected behavior? What went wrong? Chrome's limit of 6 concurrent HTTP/1 requests seems to limit the number of concurrent FetchEvents that a ServiceWorker can receive (when the site is hosted over HTTP/1). Because these are not necessarily network requests (responses may be served from cache or otherwise constructed), I think it makes more sense for this limit to apply at the network level (limit to six actual network requests). Firefox has no such limit -- I just tested 30 concurrent FetchEvents. I haven't been able to test Edge 17 or Safari 11.1 yet. The limit does not apply when the site is served over HTTP/2. Did this work before? No Does this work in other browsers? Yes Chrome version: 65.0.3325.181 Channel: stable OS Version: 10.0 Flash Version:
,
Apr 21 2018
Yep, --enable-features=NetworkService resolves it! Great news, thank you.
,
May 28 2018
|
|
►
Sign in to add a comment |
|
Comment 1 by falken@chromium.org
, Apr 20 2018Owner: falken@chromium.org
Status: Started (was: Unconfirmed)