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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]