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.
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
Last Resolved: 6 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 669259
Ah, ok. I'll move the "cause web-visible bustage" annotation to the other bug. ;)
You need to log in before you can comment on or make changes to this bug.