Possible non-compliance in response.sendRedirect
------------------------------------------------

Key: JETTY-68
URL: http://jira.codehaus.org/browse/JETTY-68
Project: Jetty
Type: Bug

Components: Servlet
Versions: 6.0.0RC0
Reporter: Tim Vernum
Priority: Minor
Attachments: ResponseTest.java

Not 100% sure if this is a bug or not.
The spec is not 100% clear, but my reading suggests that the behaviour of
Response.sendRedirect is incorrect.

The attached test shows that it is possible to change the response after calling
sendRedirect.

SRV.5.3 suggests that should not be allowed:
"These methods will have the side effect of committing the response, if it has
not already been committed, and terminating it. No further output to the client
should be made by the servlet after these methods are called. If data is written
to the response after these methods are called, the data is ignored."

However the javadoc says "After using this method, the response should be
considered to be committed and should not be written to." which implies it might
not be the container's job to enforce that the response is unchanged.



--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira



_______________________________________________
jetty-discuss mailing list
jetty-discuss@...
https://lists.sourceforge.net/lists/listinfo/jetty-discuss