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.
I also
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 the hook, since the app
code could
Greetings,
I have searched the internet and seen this same question being asked several
times but never got answered
(http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg156810.html and
http://www.junlu.com/msg/195207.html ). I also checked the Servlet 2.4 Spec and
Tomcat Docs
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, its
] wrote:
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
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 method (since
