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|REOPENED |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-01-22 14:09 ------- Unfortunately, I'm not clear on exactly what Tomcat's incorrect behavior is or whether you are expecting something that isn't currently supported. Would you please supply a simple web application that shows the problem. Please indicate how the actual result differs from what you are expecting. Note that Tomcat 3.3.1-beta1 will be released within a week, so the sooner the better. ------- Additional Comments From [EMAIL PROTECTED] 2002-02-01 05:19 ------- The handling of this is clarified in the 2.3 spec as follows: <spec-quote section="9.9.2" spec="2.3"> 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. </spec-quote> You *must* use an exception page to handle exceptions. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
