Anne van Kesteren wrote:
Or are you claiming that people who set a header to null *really* want
the specified behaviour?
It's consistent with other JavaScript APIs were null also means "null".
Overloading this API to also do removal of the header is not a goal here
and is simply a bug in Firefox as it also does that for the empty string
value (Firefox simply treats null identically to the empty string, where
other browsers treat it identically to "null".
If you don't want to specify removal, then make it either undefined
behavior, or specify that an exception must be thrown.
It's all better than to let something on the wire that the caller of the
API didn't want there in the first place.
BR, Julian
