commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15522] New: - Handle unexpected response body gracefully
Date Thu, 19 Dec 2002 10:46:14 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=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: commons-dev@jakarta.apache.org
        ReportedBy: ortwin.glueck@nose.ch


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:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message