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=24560>. 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=24560 HttpClient loops endlessly while trying to retrieve status line ------- Additional Comments From [EMAIL PROTECTED] 2003-11-11 09:09 ------- Christian, The problem here is persistent HTTP/1.1 connections. Occasionally some broken SGI scripts report content-length value that in fact does not reflect the real length of the content body sent across the wire. Consider the following: --------------------------- HTTP/1.1 200 OK Content-Length: 5 Screw you Really bad HTTP/1.1 200 OK Content-Length: 9 Ooopsie --------------------------- With the status line read loop in place HttpClient at least stands a chance of graceful recovery from this kind of mishap. Unfortunately in this situation I do not see an alternative to just scanning input stream for something that may (or may not) happen to be a valid response line So, it is paramount that the suggested check is off per default. Only in very special cases like yours one may choose to activate it. That's why the parameter is a must Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
