William A. Rowe, Jr. wrote:
At 03:04 PM 7/12/2005, William A. Rowe, Jr. wrote:
It's not the return OK; my bad. Something deeper is going on here,
some interaction with Apache 2, having to do with the request_rec
status not being bubbled back to the origin error. But if anyone
has clues to
Something's not quite right in mod_jk-land. The pertinent httpd.conf is;
ErrorDocument 404 /examplestomcat/error.jsp
Alias /examplestomcat /local0/test/webapps/examplestomcat
JkMount /examplestomcat/*.jsp ajp13
when the 404 causes error.jsp to be returned, the response code
is unset from 404
William A. Rowe, Jr. wrote:
Line 1971 of jk/native/apache-2.0/mod_jk.c says...
return OK; /* NOT r-status, even if it has changed. */
This goes back to version 1.1 of the module; the question is; WHY?
Well, mod_jk presumes that when Tomcat serves the page it is 200.
You can make a
It's not the return OK; my bad. Something deeper is going on here,
some interaction with Apache 2, having to do with the request_rec
status not being bubbled back to the origin error. But if anyone
has clues to point me at, I'd appreciate it.
At 02:52 PM 7/12/2005, William A. Rowe, Jr. wrote:
- Original Message -
From: William A. Rowe, Jr. [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Tuesday, July 12, 2005 12:52 PM
Subject: JK 1.2.14 core dump oddity
Something's not quite right in mod_jk-land. The pertinent httpd.conf is;
ErrorDocument
At 03:04 PM 7/12/2005, William A. Rowe, Jr. wrote:
It's not the return OK; my bad. Something deeper is going on here,
some interaction with Apache 2, having to do with the request_rec
status not being bubbled back to the origin error. But if anyone
has clues to point me at, I'd appreciate it.
