Closed Bug 1453318 Opened 6 years ago Closed 11 months ago

Disallow responses when a response header value contains 0x00

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
118 Branch
Tracking Status
firefox118 --- fixed

People

(Reporter: annevk, Assigned: twisniewski)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

In bug 1277019 we fixed an issue whereby we dropped part of an header value if the header value included a 0x00. This fixed several failures in the CORS test suite.

Based on discussion with Google in https://github.com/whatwg/xhr/issues/165 I'd like to suggest that when we encounter a 0x00 in a header value we consider it a network error, rather than an acceptable response.

(Network response header values are the only place where 0x00 can occur at the moment with respect to headers and Edge already does not seem to handle them whatsoever (results in infinite loading). Thus the discussion concluded that it would best if we tried to outlaw them there for consistency and somewhat closer alignment to the RFC.)

I adjusted the test added in that bug here: https://github.com/w3c/web-platform-tests/pull/10424.
Priority: -- → P2
Whiteboard: [necko-triaged]
Blocks: 1387355
Flags: needinfo?(dd.mozilla)
Flags: needinfo?(dd.mozilla)
Priority: P2 → P3
Severity: normal → S3
Assignee: nobody → twisniewski
Status: NEW → ASSIGNED
Pushed by twisniewski@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a86a27857ef6
Disallow responses when a response header value contains 0x00; r=kershaw,sunil,necko-reviewers
Flags: needinfo?(twisniewski)

How rare to be backed out for passing more web platform tests than expected. I'll push the patch again with the test metadata updated appropriately.

Flags: needinfo?(twisniewski)
Pushed by twisniewski@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cb9938ab6bca
Disallow responses when a response header value contains 0x00; r=kershaw,sunil,necko-reviewers

I suspect that I just didn't quite get the test-annotations right in the last patch. I'll do my own try-run today to check, then re-land.

https://treeherder.mozilla.org/jobs?repo=try&revision=cff7d8f7f2447d641124e896d0d620d46c5ab3b7

Flags: needinfo?(twisniewski)

Ok, the try-run seems clean, so let's try landing one more time.

Pushed by twisniewski@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8c3b9498c831
Disallow responses when a response header value contains 0x00; r=kershaw,sunil,necko-reviewers
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: