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

Re: XHR: restrictions on request headers

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 11 Apr 2006 08:19:16 +0200
Message-ID: <443B4A64.30504@gmx.de>
To: Jonas Sicking <jonas@sicking.cc>
CC: Maciej Stachowiak <mjs@apple.com>, Web APIs WG <public-webapi@w3.org>

Jonas Sicking wrote:
>> I would tentatively say the following are not valid reasons to 
>> restrict a header:
>> 4) It could result in content that the UA might not be able to parse 
>> as text or as XML (this can happen anyway with no custom headers).
> If a header will always cause the UA to not be able to parse the 
> response as neither text or XML then I think that could be disallowed. 
> There is no point in giving users a tool if the only thing they can do 
> with it is shoot themselfs in the foot.
> However I'm not sure if there are any such headers though, so this might 
> be a moot point.

I assume that user agent are allowed to extend the object to support 
binary request and response streams (such as IE does), in which case 
that restriction wouldn't make any sense...

Best regards, Julian
Received on Tuesday, 11 April 2006 06:47:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:21 UTC