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=20938>. 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=20938 Missing Content-Length header causes a SocketException ------- Additional Comments From [EMAIL PROTECTED] 2003-06-20 10:03 ------- Adrian, My rationale is that by the time decision needs to be made whether the connection is to be closed, an invalid 'Transfer-Encoding' or 'Content-Length' header would already have caused an exception. I would even go as far as saying that the check would be sufficient + if (responseHeaders.getFirstHeader("Transfer-Encoding") == null && + responseHeaders.getFirstHeader("Content-Length") == null) { + LOG.debug("Should close connection as content-length is missing."); + return true; + } Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
