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

Re: XHR: restrictions on request headers

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 11 Apr 2006 16:47:37 -0700
Message-ID: <443C4019.3000605@sicking.cc>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Maciej Stachowiak <mjs@apple.com>, Web APIs WG <public-webapi@w3.org>

Julian Reschke wrote:
> 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...

I'm not sure I follow you here.

/ Jonas
Received on Tuesday, 11 April 2006 23:47:56 GMT

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