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: Thu, 17 Nov 2011 07:14:54 +0100
Message-ID: <4EC4A65E.7020604@gmx.de>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
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.

>> - Finally, only Firefox attempts to preserve the casing of the charset
>> param - this may indicate that the workaround added for the
>> aforementioned bug isn't needed anymore.
> It indicates that the WebKit-based browsers are the only ones who end up
> with a differently-cased charset if the page does set the right charset
> in the "wrong" case.
> Whether the workaround is needed then depends on server behavior. Note
> that there were multiple servers that ran into the issue back when we
> added the workaround.

Understood. Maybe FF was the first trying the charset injection, and the 
server-side situation has improved since?

Best regards, Julian
Received on Thursday, 17 November 2011 06:15:25 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:36 UTC