DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35302>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35302





------- Additional Comments From [EMAIL PROTECTED]  2005-09-23 00:02 -------
To clarify why this patch is useful (this is the way we use the functionality).

We usually deploy several applications to a single website, requiring multiple
ISAPI redirectors.
There are a couple of cases where the connection from the web server to the
Tomcat engine can fail:
 1. The ISAPI redirector isn't installer properly as a filter
 2. The Extension side of things fails to communicate with Tomcat

We handle these errors on a site by:
 1. Putting a static page on the web server with the same name as the default
resource indicating a web server misconfiguration. If the filter doesn't work,
then this page is served.
 2. Sending a redirect to a designated static error page indicating that Tomcat
couldn't be reached when the Extension fails to communicate with Tomcat. 

Case 2 is what this patch addresses. It allows us to distinguish between generic
500 errors and those caused by the ISAPI redirector, and further allows us to
distinguish between failures to different back-end applications.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to