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 i
Thanks for the quick resopnse, Peter -
This goes back to questions I've been asking for a few weeks here,
trying to get something going whereby I can make my context paths
non-case-sensitive. After playing with filters, I finally figured out
that I could not get them to work outside of a cont
> From: David Kerber [mailto:[EMAIL PROTECTED]
> 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?
Filters are spec-compliant and per-context. Valves are Tomcat-specific
and can be per-instance. You could
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!
Da
