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 18738] - HTTPS Post Does Not Work
Date Wed, 09 Apr 2003 08:40:45 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=18738>.
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=18738

HTTPS Post Does Not Work





------- Additional Comments From olegk@apache.org  2003-04-09 08:40 -------
> the tomcat server logs only if the he can handle the request. None of
the nightly versions (0407, 0408) which I tested write a log entry.

I do not think you are right. If Tomcat drops a request for whatever reason, an 
entry stating this fact should be added to the log.

Since there's no corresponding entry in the Tomcat log, it leads me to assume 
that the request has not reached the servlet engine at all. If was dropped off 
before it could hit Tomcat. Maybe at the SSL layer or even earlier. That 
exlains why HttpClient does not receive a response. 

Are you hitting Tomcat directly or through a HTTP server? Is there a proxy or a 
firewall between the client and the server? 

Have you tried using plain HTTP? This is important. Please do test plain HTTP

> And what did I see ??? If setHttp11(false) it works fine with the tomcat. 

Sure. 'expect: 100-continue' handshake is only used with HTTP/1.1

I think something is fishy about your local setup. There have been no changes 
in the HTTP GET logic since alpha-3. HTTP GET should work in any case. Since it 
does not, I tend to believe that the problem you have been experiencing is not 
due to a flaw in HttpClient

Oleg

Mime
View raw message