Closed Bug 814103 Opened 12 years ago Closed 12 years ago

HTTP response head drops empty headers completely

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 669259

People

(Reporter: bzbarsky, Unassigned)

Details

In particular, nsHttpHeaderArray::SetHeader treats an empty value as "remove the header".  This might be OK for request headers (though that's not obvious) but for response headers this means we return null instead of "" to JS for XHR objects if the server sends "Foo: " with no value, which seems wrong.
Whiteboard: [CORS-testsuite]
Note that the issue is not SetHeader() per se: we've added a separate SetHeaderFromNet() that has different semantics (but they don't yet include keeping track of empty headers).
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Ah, ok.

I'll move the "cause web-visible bustage" annotation to the other bug.  ;)
Whiteboard: [CORS-testsuite]
You need to log in before you can comment on or make changes to this bug.