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

XHR setRequestHeader("connection", "close") is bogusly rejected

From: Morgan L <morganl.webkit@yahoo.com>
Date: Thu, 6 Mar 2008 17:55:29 -0800 (PST)
To: public-webapi@w3.org
Message-ID: <851771.94815.qm@web58415.mail.re3.yahoo.com>

Hi, I'm writing about what appears to be an error in
the XHR TR.

In section 2 of http://www.w3.org/TR/XMLHttpRequest/,
it says that setRequestHeader should reject the
connection header.

However, there are web apps in existence (e.g., Gmail)
that set the "connection: close" header to inform the
user-agent that the HTTP transaction is going to take
a long time.  (This is also informative for the
server.)  This allows a user-agent to not count this
connection against the RFC 2616 recommended maximum of
2 persistent connections per host.

So, it seems to me that the arguments
setRequestHeader("connection", "close") should be
allowed.

More details in this WebKit bug:
http://bugs.webkit.org/show_bug.cgi?id=17682

It looks like recent versions of WebKit and Gecko
block the "connection" request header per this TR. 
However, Firefox 2 does not.

--morgan


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 
Received on Friday, 7 March 2008 04:33:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 7 March 2008 04:33:46 GMT