W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: XHR content-type rewriting

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 18 Nov 2011 11:09:41 +0100
Message-ID: <4EC62EE5.3040007@gmx.de>
To: "public-webapps@w3.org" <public-webapps@w3.org>
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
Received on Friday, 18 November 2011 10:10:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT