hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38818] - Failed CONNECT leaves connection in an inconsistent state
Date Wed, 01 Mar 2006 13:20:37 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38818>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38818





------- Additional Comments From olegk@apache.org  2006-03-01 14:20 -------
(In reply to comment #3)
> Oleg,
> 
> Do you consider this a violation of the proxy protocol? I doubt that Squid is so
> bad at it.

No, I do not. This is clearly a problem on the HttpClient side

 Or do we have a chance to catch this situation and close the
> connection anyway (ignoring the keep-alive header). We can always close a
> connection without violating the HTTP specs.

This is correct. HTTP connection may be closed at any point of time without any
prior notice. 'Connection' headers are purely informational. They imply no
mandatory action.

It should be technically possible to recover from this situation without
dropping the connection, but I would rather choose to incur a slight performance
hit by reopening the connection, if the recovery logic proves too complicated.
Otherwise, it is a one line fix

Oleg


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

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org


Mime
View raw message