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=5746>. 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=5746 Settting an error page for the status code 500 doesn't display the page. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From [EMAIL PROTECTED] 2002-01-21 06:50 ------- I believe the intended way to send an error status is with sendError(). Using sendError(500) works for me. Handling for thrown exceptions is different and I assume is what this bug report is referring to. The <exception-type> element is used for assigning error pages to exceptions. The Servlet 2.2 doesn't say much about how the handling should work. The Servlet 2.3 does address this area and I am assuming that it is appropriate to take the Servet 2.3 spec as a clarification of what Servlet 2.2 should have implemented. The Servlet 2.3 spec states in SRV9.9.2: If a servlet generates an error that is not handled by the error page mechanism as described above, the container must ensure the status code of the response is set to status code 500. This says the 500 status code is applied after the handling, and doesn't imply that another pass through the handling should be done. Thus, unhandled exceptions won't be redirected to your specified "500" error page. Since sendError(500) works, I'm marking this as WORKSFORME. If I have misunderstood the bug report, reopen the bug and provide more detail. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
