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=17432>. 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=17432 '100-continue' response times out unexpectedly ------- Additional Comments From [EMAIL PROTECTED] 2003-03-03 14:45 ------- The patch does not really fix address the cause of the problem. I merely fixes RFC2616 non-compliant handling of 100 responses, which should prevent HttpClient from failing when an unexpected 100 (continue) response is received RFC2616: "10.1 Informational 1xx ... A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. ..." Vagueness of this particular paragraph begs a question. Shouldn't HttpClient ignore the complete 1xx range in order to be 100% compliant? As far as I know protocol change response (status code 101) is not currently supported Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
