[Webkit-unassigned] [Bug 17682] XHR setRequestHeader("connection", "close") is bogusly rejected

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=17682





------- Comment #10 from morganl.webkit at yahoo.com  2008-03-07 15:42 PDT -------
> We can use an attempt to set "Connection: close" as a hint not to reuse the
> connection, but I don't think it is correct to send it along as-is, nor would
> sending it along necessarily make the network layer decide that the connection
> doesn't count towards the connection limit.
> 
> If we wanted a hint that says "this may be a long-lived connection, so don't
> block other loads waiting for it", then perhaps something more explicit (like a
> property on the XHR object) would make more sense. Or perhaps we could always
> treat XHR this way. 

The behavior of existing browsers is to pass it along and to respect it on the
client side (in the manner I described).  I think it is a compat bug that
WebKit does not work this way.  I understand that this could involve changing
more than just WebKit... CFNetwork might need changes in the case of Safari. 
If the UA's network stack does not recognize this request header as a "hint",
then at least the origin server or proxy server would understand it and should
properly respond w/ "connection: close", which should cause the UA's network
stack to stop counting the connection against the max persistent connections
per host limit.  So, sending this header seems like a good thing to me.  Why do
you think it should not be sent?


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.