You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by bu...@apache.org on 2003/05/25 16:43:06 UTC
DO NOT REPLY [Bug 20198] -
HttpClient drops connection to the proxy when an invalid 'connection: close' directive is encountered in 'connection established' response
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20198>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20198
HttpClient drops connection to the proxy when an invalid 'connection: close' directive is encountered in 'connection established' response
olegk@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Major |Enhancement
Priority|Other |Low
Summary|hhtpClient failed to work |HttpClient drops connection
|with IBM Web Traffic Express|to the proxy when an invalid
|Caching proxy on https |'connection: close'
| |directive is encountered in
| |'connection established'
| |response
Target Milestone|--- |2.0 Beta 2
------- Additional Comments From olegk@apache.org 2003-05-25 14:43 -------
Bin,
I see things a bit differently here. It is not HttpClient that fails to work
with IBM Web Traffic Express Caching proxy on https, rather it is IBM Web
Traffic Express Caching proxy that fails to work properly. Sending 'connection:
close' header along with connection established response appears ... well... odd
to me. So, the bug report should have gone to the IBM folks in the very first
place.
Nevertheless, HttpClient has been tweaked to ignore inappropriate 'connection'
directives in order to make it more robust when dealing with non-compliant proxy
servers.
The patch attached will also make HttpClient report a waring when an invalid
'connection: close' directive is encountered in 'connection established' response.
Oleg