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

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

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 10 Mar 2008 18:07:31 -0700
Cc: Kris Zyp <kzyp@sitepen.com>, Morgan L <morganl.webkit@yahoo.com>, public-webapi@w3.org
Message-Id: <EA0E1E2B-266C-4680-AF79-4719359BBDAE@apple.com>
To: Jonas Sicking <jonas@sicking.cc>


On Mar 10, 2008, at 4:37 PM, Jonas Sicking wrote:

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

A commenter on this WebKit bug said so: <http://bugs.webkit.org/show_bug.cgi?id=17682 
 >. But further testing does not seem to bear out this claim.

Regards,
Maciej
Received on Tuesday, 11 March 2008 01:18:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 March 2008 01:18:42 GMT