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 20198] New: - hhtpClient failed to work with IBM Web Traffic Express Caching proxy on https
Date Fri, 23 May 2003 20:35:27 GMT
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

hhtpClient failed to work with IBM Web Traffic Express Caching proxy on https

           Summary: hhtpClient failed to work with IBM Web Traffic Express
                    Caching proxy on https
           Product: Commons
           Version: Nightly Builds
          Platform: PC
        OS/Version: Windows 9x
            Status: NEW
          Severity: Major
          Priority: Other
         Component: HttpClient
        AssignedTo: commons-httpclient-dev@jakarta.apache.org
        ReportedBy: bin.chen@sabre-holdings.com


One of our customer is using our application to connect to our servlet using 
https.  We are using httpClient for http protocol handling.  The customer has a 
IBM proxy (see log file).  The connect failed with a null pointer exception.

The log seem to indicate that the proxy server is returning 200 for "CONNECT", 
but the proxy also sends a "Connection:close" header.  The httpClient closed 
the connection and then tried to create the SSL socket.  If the proxy server is 
incorrect in sending 200 with "Connection:close", then httpClient should throw 
exception for invalid state (IllegalStateException ?).

I will attach the log file.

Mime
View raw message