[Bug 16303] meaning of "all" charset parameters of content-type header

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16303

--- Comment #17 from Julian Reschke <julian.reschke@gmx.de> 2012-04-12 10:05:59 UTC ---
(In reply to comment #16)
> Because setRequestHeader() would have to get special purpose parsers. That's
> not how setRequestHeader() works.

"For setRequestHeader() if possible, otherwise for send()."

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 12 April 2012 10:06:11 UTC