On 2011-11-17 07:14, Julian Reschke wrote:
On 2011-11-17 01:55, Boris Zbarsky wrote:
On 11/17/11 2:18 AM, Julian Reschke wrote:
- Opera and IE do not rewrite the type; so if the caller sets the wrong
charset, this is what is sent to the server
Which on the face of it is broken....
Absolutely. It would be less broken spec-wise if XHR stated that adding
the charset in setRequestHeader is illegal. Minimally, it should
recommend not to include it as it's pointless.
...
Such as:
"Specifying the charset in the Content-Type header field is pointless
because the encoding of the payload is controlled by the User Agent and
hardwired to UTF-8."
(as opposed to just writing the specs for the browser implementors and
leaving web authors guessing)
Best regards, Julian
