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=15522>. 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=15522 Handle unexpected response body gracefully Summary: Handle unexpected response body gracefully Product: Commons Version: 2.0 Alpha 1 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: HttpClient AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Apache's HTTPD sends a response body after a HEAD request to a authenticating realm even though the headers do not signal a body (no Transfer-Encoding / Content-Length). We need to be able to determine if a response body follows after the headers, even though the headers do not signal a following body. Need non-blocking HttpConnection.isDataAvailable(): A small (~ 1KB) FIFO buffer needs to be used here. This also allows us to peek into the stream and look what sort of data is there before we actually read from the stream. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
