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=17821>. 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=17821 100-Continue Error ------- Additional Comments From [EMAIL PROTECTED] 2003-03-10 17:21 ------- Several observations can be made analysing squid access log attached above: 1) Mozilla 1.2.1 appears to not be using "Expect: 100-continue" handshake when sending POST requests via HTTP proxy 2) Squid does not seem to honour "Expect: 100-continue" protocol. Squid happily returns 100 status code and closes the connection to the remote host. The question here if who is at fault here: Squid or HttpClient? Can it be that Squid expects additional conditions to be met, for instance [Proxy-Connection: keep-alive\r\n] is expected to be present? Regardless whose fault it might be, I suspect many HTTP proxy may have various issues with "Expect: 100-continue" handshake. To be on a safe side, I suggest "Expect: 100-continue" handshake be disabled when sending entity enclosing requests via a HTTP proxy. Comments, ideas, suggestions? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
