Error Page Not Working - Tomcat 5.5.15
Subject: RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
Thanks, Chuck.
In my case, the default servlet/container DID send the HTTP 503 error
back, displaying the error with the Tomcat default 503 error page, instead
of the custom error page.
"Caldarale, Charles R" <[EMAIL PROTECTED]> wrote:
> From: Yue Mu [mailto:[EMAIL PROTECTED]
> Subject: RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
>
> If the sendError method is called on the response,
I think the above clause lets the container off
> From: Yue Mu [mailto:[EMAIL PROTECTED]
> Subject: RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
>
> If the sendError method is called on the response,
I think the above clause lets the container off the hook, since the app
code could not have used the sendError m
Thanks, Charles.
I should have mentioned that I have tried to use the global web.xml but it
does not work either. (Just keep the error pages in the same place, and add the
's in the global web.xml in $TOMCAT_HOME/conf)
According to the spec, it should catch 4xx and 5xx.
From S
> From: Yue Mu [mailto:[EMAIL PROTECTED]
> Subject: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15
>
> However, when the web application is stopped (unavailable),
> it returns the default Tomcat 503 error page (see below),
> not the custom error page.
If the application is not available,
