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

Re: XMLHttpRequest.getResponseHeader and missing headers

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 10 Aug 2006 11:31:57 +0200
To: "Alexey Proskuryakov" <aproskuryakov@gmail.com>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <op.td193jbk64w2qv@id-c0020.oslo.opera.com>

On Tue, 20 Jun 2006 13:38:19 +0200, Alexey Proskuryakov  
<aproskuryakov@gmail.com> wrote:
> "If no headers of that name were received, then it MUST return the
> empty string."
>
>   This matches the behavior of Internet Explorer and Opera 9, but not
> of Firefox 1.5 or Safari 2 (the former returns null, while the latter
> returns undefined).
>
>   I don't see any restriction on the semantics of empty vs. missing
> headers in RFC 2616, and indeed, the difference is sometimes
> significant, at least in the case of requests (SOAP, Atom API). Thus,
> the Firefox behavior appears the most reasonable to me. It is
> documented in the idl at
> <http://lxr.mozilla.org/mozilla/source/content/base/public/nsIXMLHttpRequest.idl#148>.
>
>   Can the specification be adjusted to match it at this point?

Yeah, fair enough. It also seems more consistent with other methods.

Now I wonder if it should be null before readyState is 3 or 4 as well...


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Thursday, 10 August 2006 09:32:14 GMT

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