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

Re: XHR setting headers

From: Subbu Allamaraju <subbu@subbu.org>
Date: Tue, 13 May 2008 16:29:48 -0700
Cc: Anne van Kesteren <annevk@opera.com>, Peter Michaux <petermichaux@gmail.com>, public-webapi@w3.org
Message-Id: <309E7528-D2A6-42A5-B384-D514C70F1AA3@subbu.org>
To: Julian Reschke <julian.reschke@gmx.de>

On May 13, 2008, at 12:24 AM, Julian Reschke 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?

I don't think this is "pre-filling", but some defaults applied by an  
implementation. A removeHeader() may not fix this specific problem.

Received on Tuesday, 13 May 2008 23:30:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 13 May 2008 23:30:27 GMT