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=16508>. 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=16508 Response is not being committed after RequestDispatcher forward Summary: Response is not being committed after RequestDispatcher forward Product: Tomcat 4 Version: 4.1.18 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I upgraged from Tomcat 4.1.12 to 4.1.18 and discovered new behavior with the RequestDispatcher. After the forward method, the response is no longer being committed. I believe this is a bug. Acording to the Servlet 2.3 spec, section 8.4. It says, "Before the forward method of the RequestDispatcher interface returns, the response content must be sent and committed, and closed by the servlet container." With tomcat 4.1.18 this is not true. After the forward method, if you call response.isCommitted() it returns false. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>