You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by David Kerber <dc...@verizon.net> on 2006/03/10 19:02:38 UTC

Are filters restricted to be within contexts?

Basically, I'd like to know if a filter can be used to change a context 
path, or are they restricted to acting within a given context?

For example, can I set up a filter at a higher level, so that it will 
trigger even on a context that doesn't exist in the current Tomcat instance?


Thanks!
Dave



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Are filters restricted to be within contexts?

Posted by David Smith <dn...@cornell.edu>.
Any request not matching a specific webapp's path belongs to the ROOT
webapp.  Place filters there if you'd like to catch requests to
non-existent webapps.  Otherwise if a request matches a webapp, that
webapp's filters are run instead.

--David

David Kerber wrote:

> Basically, I'd like to know if a filter can be used to change a
> context path, or are they restricted to acting within a given context?
>
> For example, can I set up a filter at a higher level, so that it will
> trigger even on a context that doesn't exist in the current Tomcat
> instance?
>
>
> Thanks!
> Dave
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org