Open Bug 1597115 Opened 6 years ago Updated 4 years ago

Weird behavior with HTTP/2 HEAD responses that contain long headers

Categories

(Core :: Networking: HTTP, defect, P3)

Product:
Core
Component:
Networking: HTTP
Version:
70 Branch
Type:
defect

Tracking

()

People

(Reporter: apyrgio, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0

Steps to reproduce:

A server returned an HTTP/2 HEAD response that contained a long (~100,000 chars) HTTP header.

(You can find an easy way to reproduce this issue here: https://github.com/apyrgio/firefox-http2-head-issue)

Actual results:

Firefox took a long time (~1 minute) to complete the request,. Ultimately, it failed, but the status code in the Network tab showed up as 200.

Note that the same GET and HTTP/1.0 HEAD requests completed successfully.

Expected results:

That depends on what is the header size limit of Firefox. If the response exceeded that limit, Firefox should explicitly state so. If not, the response should be handled properly.

Component: Untriaged → Networking: HTTP
Product: Firefox → Core

I will investigate.

Assignee: nobody → dd.mozilla
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Priority: -- → P2
Whiteboard: [necko-triaged]

It's been a few months since the last update on this issue. Did you manage to reproduce it?

Assignee: dd.mozilla → nobody
Blocks: 1711687
Severity: normal → S4
Status: ASSIGNED → NEW
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.