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

XMLHttpRequest.getResponseHeader and missing headers

From: Alexey Proskuryakov <aproskuryakov@gmail.com>
Date: Tue, 20 Jun 2006 15:38:19 +0400
Message-ID: <4edacb3a0606200438k29956854k41080ef603506cc9@mail.gmail.com>
To: public-webapi@w3.org

"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?

- WBR, Alexey Proskuryakov
Received on Tuesday, 20 June 2006 17:31:30 GMT

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