- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Fri, 15 Jun 2007 12:08:40 -0500
- 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 UTC