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

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

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 10 Mar 2008 16:37:40 -0700
Message-ID: <47D5C644.30707@sicking.cc>
To: Kris Zyp <kzyp@sitepen.com>
CC: Morgan L <morganl.webkit@yahoo.com>, public-webapi@w3.org

Kris Zyp wrote:
>>> 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.
> As far as I can tell, Firefox is the only browser that regards 
> "connection: close" as an indication that the connection should not be 
> counted against the connection limit

What gives you that idea? I'm not actually sure since I don't know the 
inner workings of the network code, but I have never heard of such behavior.

And in any case Firefox 3 does not even let you set the Connection 
header using XHR.

/ Jonas
Received on Monday, 10 March 2008 23:38:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 March 2008 23:38:11 GMT