Hi Eric,
Eric B. wrote:
Sorry - I guess I wasn't specific enough. The HTTP status code that I got
from Apache was 200 hence the OK. I assumed that it was probably 200 since
I was actually able to communicate with Apache itself, even though its
request to tomcat was unavailable. Or unless I am missing something in my
apache configuration to display the correct error page.
If I check the headers sent using Fiddler, I get the following:
HTTP/1.1 200 OK
Date: Fri, 07 Sep 2007 18:04:51 GMT
Server: Apache/2.0.52 (White Box)
Content-Length: 501
Connection: close
Content-Type: text/html; charset=iso-8859-1
However, it is definitely not "OK" b/c my tomcat server is down.
Do I have something foobar'ed in my apache config? Or is it a problem in my
mod_jk params? If it makes any difference, I am running mod_jk v1.2.10 w/
Apache 2.0.52.
JK version 1.2.10 is very old. A lot of things changed until we now
reached 1.2.25. Typically backend problems will be answered with a non
200 status code. Try a more recent version (like 1.2.25).
Concerning error pages: In case Tomcat already sends an error status
code, your webapps error page will be used. In case JK generates the
error code itself, because it has trouble with the backend, the Apache
httpd error page will be used.
Thanks,
Eric
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
