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

Re: removeRequestHeader()

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 26 May 2008 13:11:42 +0200
Message-ID: <483A9AEE.1030709@gmx.de>
To: Anne van Kesteren <annevk@opera.com>
CC: Maciej Stachowiak <mjs@apple.com>, Laurens Holst <lholst@students.cs.uu.nl>, public-webapi@w3.org

Anne van Kesteren wrote:
> On Mon, 26 May 2008 10:00:26 +0200, Maciej Stachowiak <mjs@apple.com> 
> wrote:
>> I am ok with deferring such a mechanism to XHR2 however. In WebKit 
>> we'll likely implement it equally quickly whether it is in XHR1 or 
>> XHR2 since it seems like useful functionality. But there are 
>> complications, namely, how does it interact with headers that are set 
>> automatically by the UA?
> 
> It's not clear to me at all what problem it solves. The examples given 
> so far are all UA bugs.

The problem that needs to be solved is that clients need a reliable way 
to set a header.

Issues with the current spec are:

- implementations that preset headers on object creation

- implementations *adding* values before the request is being made

- library code that acts on an existing XHR instance but did not create
it, thus has no way what headers already have been set

(the last one IMHO is the most important one, and the one that really 
requires new functionality)

BR, Julian
Received on Monday, 26 May 2008 11:12:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 26 May 2008 11:12:33 GMT