tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32604] - Some httpHeaders can be lost in response
Date Wed, 12 Jan 2005 01:35:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32604>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32604





------- Additional Comments From jan.luehe@sun.com  2005-01-12 02:35 -------
I agree with Remy here that response.setContentLength(0) would cause the
response to be closed, because it meets the condition that the amount of content
specified in the setContentLength method of the response (in this case: zero)
has been written to the response.

Julian/Touchard, the reason the response is considered committed from the
implementation point of view is because getContentCount() and getContentLength()
are both zero in:

    public boolean isAppCommitted() {
        return (this.appCommitted || isCommitted() || isSuspended()
                || ((getContentLength() != -1) 
                    && (getContentCount() >= getContentLength())));
    }

Please notice that getContentCount() really only returns the number of bytes
written to the response body (in this case: zero): it does not include any
response header bytes, which - I agree with you - would be wrong.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message