Open
Bug 1282426
Opened 8 years ago
Updated 2 years ago
fetch spec requires lower case headers, but UA added headers are mixed case
Categories
(Core :: Networking, defect, P5)
Core
Networking
Tracking
()
NEW
People
(Reporter: bkelly, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-would-take])
Currently the fetch spec requires that headers be normalized to lower case. We do this in our dom/fetch/Headers.h object. We don't, however, do anything like this for headers added in necko or non-fetch parts of the tree. Is this something we should implement or should we push back on the spec? It seems making this change could break things for buggy servers, etc.
Comment 1•8 years ago
|
||
I think we should do what I and others outlined in https://github.com/whatwg/fetch/issues/304#issuecomment-219630716 and onward.
Comment 2•7 years ago
|
||
See https://github.com/whatwg/fetch/pull/476 for the overall change to Fetch to stop lowercasing header names. It seems this might still affect us as Headers should no longer lowercase header names on input either, only on output.
Comment 3•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•