W3C home > Mailing lists > Public > public-webapi@w3.org > June 2007

Re: Recent spec change to XMLHttpRequest default Content-Type

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 15 Jun 2007 12:08:40 -0500
Message-ID: <4672C798.7070909@mit.edu>
To: Carsten Orthbandt <carsten@pixeltamer.net>
CC: public-webapi@w3.org

Carsten Orthbandt wrote:
> The (IMHO) valid reason here is:
> - redundant header overhead
> - the UA isn't even meant to interpret the response, so it doesn't need
>   any information on how to parse it

Actually, you're expecting the UA to convert the bytes in the response into 
characters in this case.  Ideally, you would be sending a Content-Type header 
with a charset parameter if you want that sort of thing to be happening...

-Boris
Received on Friday, 15 June 2007 17:08:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:57 GMT