RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15

2006-02-05 Thread Yue Mu
"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

RE: Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15

2006-02-04 Thread Yue Mu
PROTECTED]> 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 pag

Custom HTTP 503 Error Page Not Working - Tomcat 5.5.15

2006-02-04 Thread Yue Mu
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

Re: request.getHeader() gives null

2006-02-04 Thread Yue Mu
HI Anoop, >> Is it that the response of the first page becomes the request of the next jsp No - "the next jsp" gets the same request, which is the whole idea of "forwarding" a request. This is why you don't see the newly added headers (to the response!). I'm not sure what