You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/05/30 12:17:34 UTC

DO NOT REPLY [Bug 20307] - Setting content length causes Tomcat to ignore response status

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=20307>.
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=20307

Setting content length causes Tomcat to ignore response status

remm@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From remm@apache.org  2003-05-30 10:17 -------
It took me about 15 minutes to figure out what was going on.

The response is considered committed as soon as the amount of bytes specified in
the content length has been written. Since the content length is 0, the response
is considered committed as soon you call response.setContentLength(0). Since you
can't change the status after the response has been committed, that's why you
get a 200 status back.

This spec seems a bit weird in that case.

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