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 ------- Additional Comments From [EMAIL PROTECTED] 2003-05-27 18:22 ------- Bin, I apologize if mine of Mike's statements turned out to be confusing or contradictory. In fact, since beta-1 HttpClient does ignore 'connection: close' header (as well as all other headers) when Connect method returns status code 200, and therefore should work with non-compliant proxy servers including IBM Web Traffic Express that one of your clients is using. I stumbled upon the problem pretty much by chance just a day before you filed the report. http://cvs.apache.org/viewcvs/jakarta-commons/httpclient/src/java/org/apache/commons/httpclient/ConnectMethod.java.diff?r1=1.14&r2=1.15 My latest patch merely added a warning for non-compliant behaviour. I hope that clarified things a bit. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
