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 32811] - sendRedirect does not commit
Date Wed, 05 Jan 2005 01:38:50 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=32811>.
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=32811





------- Additional Comments From wpoziombka@budweiser.com  2005-01-05 02:38 -------
(In reply to comment #6)
> No, the client may have received other bytes prior to the redirect, e.g. the 
> content length or other headers.   

The first line of a response is the status line.  So, a redirect (302 -
SC_FOUND) cannot be sent after any other byte.  If the client has received bytes
the response should be considered committed and subsiquent calls to sendRedirect
should throw an exception.  However, that is not even the issue here.  

The issue is that the sendRedirect does not commit the response (as the spec
defines in its description of isCommitted).  The sendRedirect does not send the
302 status line to the client prior to an exception.  When an exception occurs
the buffer is reset and a 500 is sent instead.  It seems that the client should
still receive a 302 (SC_FOUND).  It appears that this is how other servlet
containers have interpreted the specification.

-- 
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