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=37550>. 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=37550 ------- Additional Comments From [EMAIL PROTECTED] 2005-11-18 00:14 ------- (In reply to comment #4) > You see, HttpClient sends the initial request line with HTTP/1.1. If the proxy > does not support HTTP 1.1 it should have returned an appropriate status. But > the > proxy misbehaves and a) only notices that we use HTTP 1.1 when we use chunking > b) just drops the connection leaving us without any information about what's > the > problem. So how should HttpClient know to fall back to 1.0? We used the tcp tunnel to watch what was sent from the applet to the proxy and what the proxy sent back to us. It's not true that the proxy just dropped the connection. It sent us back a 501 and some pretty HTML to indicate that the operation/protocol the client requested wasn't supported. On one occasion we were able to read the status line in the client without getting the socket closed exception. However, after that we've only seen the closed socket exception which is demonstrated in the wire log. I'm using the MTHCM and I believe only one thread is interacting with HttpClient at this point. Any clues about the class(es) I should look at to see why the connection is being closed on the client side without first reading the response? Rob -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
