W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

Re: [XHR] Some comments on "charset" in the Content-Type header

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 19 Sep 2008 16:55:29 +0200
Message-ID: <48D3BD61.7070003@gmx.de>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: Anne van Kesteren <annevk@opera.com>, public-webapps <public-webapps@w3.org>

Boris Zbarsky wrote:
> 
> OK, more data in 
> <https://bugzilla.mozilla.org/show_bug.cgi?id=416178#c27> comes down to:
> 
> 1)  The firewall is filtering out anything that does not have a
>     Content-Type header string value of exactly
>     "application/x-www-form-urlencoded".
> 2)  They'd really like to have a way of not sending a charset.
> 
> They claim to not have a way to modify the firewall configuration from 
> the above behavior, which I guess is no more surprising than any of a 
> variety of other hardcoded idiocies we've been encountering in HTTP 
> server behavior.

Maybe I'm missing something, but why not leave it alone if the MIME type 
isn't "text/*" (the only ones where charset is really relevant)?

BR, Julian
Received on Friday, 19 September 2008 14:56:21 GMT

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