Re: XHR setting headers

• From: Julian Reschke <julian.reschke@gmx.de>
• Date: Mon, 12 May 2008 17:24:16 +0200
• To: Anne van Kesteren <annevk@opera.com>
• CC: Peter Michaux <petermichaux@gmail.com>, public-webapi@w3.org
• Message-ID: <48286120.7000304@gmx.de>

Anne van Kesteren wrote:
> On Thu, 17 Apr 2008 15:31:37 +0200, Julian Reschke 
> <julian.reschke@gmx.de> wrote:
>> The whole "append" semantics is problematic as long as the user can't 
>> find out what the current value is.
>>
>> IMHO we need either removeRequestHeader(), getRequestHeader(), or both.
> 
> Yes, you have already stated this before. So far, there does not seem to 
> be too much demand for these features and they would either way be out 
> of scope for XMLHttpRequest Level 1 at this point.

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).

BR, Julian

Received on Monday, 12 May 2008 15:24:58 UTC