W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: XHR: restrictions on request headers

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 14 Apr 2006 10:27:15 +0200
To: Ian Hickson <ian@hixie.ch>
Cc: Web APIs WG <public-webapi@w3.org>
Message-ID: <pnmu32ts61hu0l5mcrchj6hae0nm1dr72a@hive.bjoern.hoehrmann.de>

* Ian Hickson wrote:
>Accept-Charset was the one that has been mentioned several times -- 
>certainly unrestricting it (making it accept things that the UA won't know 
>how to handle) doesn't seem very useful, since the UA will be unable to 
>provide either a responseXML or responseText in that case.

Unless it is somehow guranteed that the response is in UTF-8 or UTF-16
scripts would have to deal with this in any case since the response may
use an unsupported encoding no matter what the Accept-Charset header is
set to, especially if implementations don't use *;q=0 or equivalent.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Friday, 14 April 2006 08:27:36 GMT

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