Re: error-page directive does not catch HTTP STATUS 500 errors!

[Moritz Mann <mo...@open.ch>]

Thank you Remy for your input!

I hope that this Status Http 500 bug is the same like the Http Status
403 bug you have mentioned.

moritz

Remy Maucherat wrote:
> 
> > Hi all,
> >
> > I am using a tomcat 4.0.1 standalone running on Unix. I configured my
> > web.xml like the following:
> >
> > <error-page>
> >     <exception-type>java.lang.Throwable</exception-type>
> >     <location>/errors/err-except.html</location>
> > </error-page>
> > <error-page>
> >     <error-code>500</error-code>
> >     <location>/errors/err-code500.html</location>
> > </error-page>
> > <error-page>
> >     <error-code>404</error-code>
> >     <location>/errors/err-code404.html</location>
> > </error-page>
> >
> >
> >
> > the code should catch all error codes - but unfortunately it does not.
> > On HTTP STATUS 500
> > errors a <page cannot be displayed> appears. I crawled the web for this
> > issue but i did not find anything about it.
> >
> > In my WEB-INF/web.xml i created the following constraint in order to
> > generate a HTTP STATUS 500 error.
> >
> > <security-constraint>
> >         <web-resource-collection>
> >                 <web-resource-name>no-access</web-resource-name>
> >                 <url-pattern>/test.html</url-pattern>
> >         </web-resource-collection>
> >         <auth-constraint>
> >                 <role-name>nobody</role-name>
> >         </auth-constraint>
> > </security-constraint>
> >
> > Did anyone already have found a solution?
> 
> This looks similar to http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5725
> 
> Remy
> 
> --
> To unsubscribe:   <ma...@jakarta.apache.org>
> For additional commands: <ma...@jakarta.apache.org>
> Troubles with the list: <ma...@jakarta.apache.org>

-- 
moritz mann
junior engineer

open systems ag
raeffelstrasse 29
ch-8045 zurich
t: +41 1 455 74 00
f: +41 1 455 74 01
mailto:moritz@open.ch

http://www.open.ch

Re: error-page directive does not catch HTTP STATUS 500 errors!

[Remy Maucherat <re...@apache.org>]

> Thank you Remy for your input!
> 
> I hope that this Status Http 500 bug is the same like the Http Status
> 403 bug you have mentioned.

If the request was not completely mapped, then it should be the same.
There should be a NPE in the logs if that's the case.

If you want to test it, you can try 4.0.2 b1 or a nigtly build.

Remy


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>