New issue
Advanced search Search tips

Issue 835448 link

Starred by 4 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocked on:
issue 715640



Sign in to add a comment

Limited to 6 concurrent ServiceWorker FetchEvents when using HTTP/1

Reported by zbbjorn...@gmail.com, Apr 20 2018

Issue description

UserAgent: 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:
 

Comment 1 by falken@chromium.org, Apr 20 2018

Blockedon: 715640
Owner: falken@chromium.org
Status: Started (was: Unconfirmed)
I expect this is fixed with NetworkService/S13nServiceWorker.

You could try it out by running Chrome with --enable-features=NetworkService.

Marking as "Started" as  bug 715640  is started.
Yep, --enable-features=NetworkService resolves it! Great news, thank you.

Comment 3 by falken@chromium.org, May 28 2018

Cc: falken@chromium.org tbansal@chromium.org
 Issue 846382  has been merged into this issue.

Sign in to add a comment