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 --- Additional Comments From [EMAIL PROTECTED] 2003-05-28 06:44 --- Bin, The only way to fix the problem in your production environment will be to upgrade to beta-1. This should be an easy upgrade because your version (0308) is a post alpha-3 version. So the differences will be small (the diff is huge though) on the API level. You should at least give it a try. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- Additional Comments From [EMAIL PROTECTED] 2003-05-27 17:20 --- Mike and Oleg, First as confirmation, we are using an old version of the nightly build (0308 build modified by us). I am not sure if we can afford to upgrade in this case. To clarify the situation, let me give a brief description of our application. Our application is actually a signed applet and the size of the applet is fairly large. So we actually have our customers installing all the jar files (including httpClient) on the client machine. The applet is used by several thousands customers worldwide. As result, upgrading is a big deal (not simply a technical decision). The applet is using http/https to communicate with our web/app server and httpClient is used for the http communication. Currently, we released our product with the modified 0308 nightly build (we could not make the latest nightly build work within our release schedule). After the release, we made the attempt to find a way to work with latest build and with the great help from you guys we got there. But the new code is not in the release yet. Also our average users are not very comfortable with computers so it is rather difficult to make our users to test different scenarios. Now this bug is reported from the field and the customer is still using the old code. Now come back to the bug. If I read your comments correctly, then 1. The bug was caused by the incorrect behavior of IBM proxy server (200 with connection:close). 2. The latest nightly build (or coming beta) will handle the error better, but it still would not work. For point 1, I agree with that assessment. For point 2, I would like to know what will be the expected behavior (logging some warning or throwing exceptions). Given that I do not have the environment to reproduce the problem, I may have to let our customers do the test. So I would need to know what to expect. Finally, I know that the httpClient is close to beta 2 and this should not stop it. But I hope this can be addressed in some later version. Our customer have tried to use our application with browser connection (one of the things applet can do), it did navigate through the proxy server OK. I would think that httpClient can also work with the situation and find a way to work with this incorrect proxy server behavior (may be ignoring the connection:close when 200 is returned?). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 --- 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.14r2=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]
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 --- Additional Comments From [EMAIL PROTECTED] 2003-05-27 19:33 --- Bin, Beta-1 has been tagged in the CVS two days ago is officially out. Unfortunately, Jeff Jandalf, our release prime, has been staying off-line for quite some time. We can't deploy the official build without him, as only Jeff has necessary access permissions for the official Jakarta file repository web site. That should not stop you from obtaining the beta-1 release, though. Just get it from the CVS by running the following command: cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co -r HTTPCLIENT_2_0_BETA1 jakarta-commons/httpclient Cheers Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
