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=29583>. 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=29583 Filters not invoked on error pages Summary: Filters not invoked on error pages Product: Tomcat 4 Version: 4.1.24 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Error pages, for example a 403 page to display rejected logins, declared in the web.xml are not submitted to the filters chain. Tomcat seems to create a new request and invokes the declared resource (servlet or struts action) directly. In my case, a filter wraps the request that takes decision depending on the requested URI. When the error-page is invoked, the request URI is not the one the UA is expecting, and any path calculated from it leads the client to fail. So, two questions : 1) Is it a normal behaviour not to invoke the filter chain in this case ? 2) Is it a normal behaviour to ignore the previous request, that already has passed by the all needed filters and has been wrapped, and replace it with a new one ? If not, is there any fix in a more recent version ? Thanks for responses. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
