W3C home > Mailing lists > Public > public-webapi@w3.org > May 2008

Re: XHR setting headers

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 27 May 2008 14:14:02 +0200
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: "Peter Michaux" <petermichaux@gmail.com>, public-webapi@w3.org
Message-ID: <op.ubtaxonb64w2qv@annevk-t60.oslo.opera.com>

On Tue, 13 May 2008 09:24:42 +0200, Julian Reschke <julian.reschke@gmx.de>  
wrote:
> Anne van Kesteren wrote:
>> On Mon, 12 May 2008 17:24:16 +0200, Julian Reschke  
>> <julian.reschke@gmx.de> wrote:
>>> Well, we just heard from people complaining about XHR implementations  
>>> pre-filling request headers, and thus causing clients to create broken  
>>> content-type headers (because of the append functionality).
>>  Actually, that was specifically about Accept and it seems to be simply  
>> an Opera bug per the specification.
>
> So does the specification say which headers may be prefilled by the  
> implementation, and when?

It is now made clear that user agents can only control the headers that  
authors can not set and can control a limited set of headers if the author  
has not set them (e.g. the specification allows the author to control  
caching himself, but if he does not do that the user agent can do it).


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Tuesday, 27 May 2008 12:14:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 May 2008 12:14:28 GMT