1759966 - Http Request failed with network.http.spdy.enabled.http2 enabled

Status: RESOLVED INCOMPLETE

(Core :: Networking: HTTP, defect)

Description

[lliu]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36

Steps to reproduce:

Our platform sends concurrent(3) http PUT requests to upload file chunks. Each request carries maximum ~4MB in the payload.

A http request example:

PUT /chunk/2bccbd2f38f15c13eb7d5a89fd9d85f595e23bc3-4194304
Host: xxxxxx
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:97.0) Gecko/20100101 Firefox/97.0
Accept: /
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Content-Length: 4194304
X-Client-Id: xxxxx
Origin: https://hello.atlassian.net
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site
Referer: https://hello.atlassian.net/
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
TE: trailers

Actual results:

We observed on firefox that some request will take longer waiting for response, and finally fail with a 502 Bad Gateway. While this won't happen on Chrome.

Referred from another similar issue(we have the same Browser <-> ALB infrastructure): https://bugzilla.mozilla.org/show_bug.cgi?id=1518622

We turned off network.http.spdy.enabled.http2, which was set to true by default.
Then no response delay or failure occurred.

Expected results:

We suspect that Firefox speedy http2 may somehow interrupt the request concurrency, and then block single request to be sent randomly.

We are investigating the ALB side at the same time, but based on the fact that chrome works fine. We thought it would be better to contact Firefox team to look at this issue.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Networking: HTTP' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Dragana Damjanovic [:dragana]]

Can you please create a http log.

If you do not want to attach it here please send it to [e-mail].
Please note that log may contain cookies and all URL you are browsing. We recommend to use a clean profile and do not log into website.

Comment 3

[lliu]

(In reply to Dragana Damjanovic [:dragana] from comment #2)

Can you please create a http log.

If you do not want to attach it here please send it to [e-mail].
Please note that log may contain cookies and all URL you are browsing. We recommend to use a clean profile and do not log into website.

Thanks, logs sent to that email addr. Please let me know if you need more info.

Comment 4

[Kershaw Chang [:kershaw] PTO until Jan 2]

The log indicates this might be related to service worker.
Are you able to reproduce this without service worker?

Comment 5

[lliu]

(In reply to Kershaw Chang [:kershaw] from comment #4)

The log indicates this might be related to service worker.
Are you able to reproduce this without service worker?

Hey Kershaw, the issue is still reproducible by disabling service worker.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:dragana, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 7

[lliu]

Hi team, any updates on this ticket? Thanks.

Comment 8

[Dragana Damjanovic [:dragana]]

Removing need-info and returning bug to the triage queue.

Comment 9

[(PTO until Jan 6) Valentin Gosu [:valentin] (he/him)]

Hi reporter, are you still seeing this bug in the latest Firefox?

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:kershaw, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 11

[(PTO until Jan 6) Valentin Gosu [:valentin] (he/him)]

It seems we don't have enough info to complete this bug.
@reporter - please reopen if you are still seeing this issue and can assist us with more info.