W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: [xhr] Appending a charset after an author added content-type

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 19 Feb 2013 20:09:41 +0100
Message-ID: <5123CDF5.10305@gmx.de>
To: Anne van Kesteren <annevk@annevk.nl>
CC: Boris Zbarsky <bzbarsky@mit.edu>, public-webapps@w3.org
On 2013-02-19 19:51, Anne van Kesteren wrote:
> On Tue, Feb 19, 2013 at 6:44 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> Note that Firefox adds the charset even if it wasn't set by the page because
>> web developers were asking for it to aid server-side processing...  The
>> alternative is that the server has no idea what to do with the data.  :(
>
> Does that include cases though where the page did set a Content-Type
> through setRequestHeader()? Because technically what Firefox does
> violates HTTP semantics as not every MIME type allows for a charset
> parameter.

Right. If other UAs don't do this, FF should avoid it as well.

Which reminds me about the funny requirement to rewrite charset 
parameters in place; this really needs test cases; if it's still only 
Firefox doing it it should be nuked from the spec.

Best regards, Julian
Received on Tuesday, 19 February 2013 19:10:11 GMT

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