Tomcat 5.0 web.xml filter mapping <url-pattern>/content/*.jsp - Java

P.Hill wrote:
> <filter-mapping>
> <filter-name>foo.bar.MyFilter</filter-name>
> <url-pattern>/content/*.jsp</url-pattern>
> </filter-mapping>

Upon further reading, I have discovered that my
friend can't be trusted. *.jsp doesn't work in
4.1, and it complains as I reported in 5.0.

My solution at this time is to allow requests
for things other than jsps through the same
filter to skip the filtering, since the filter
doesn't need to kick in just because someone
is asking for background.jpg or some such.

Yeah, I know we might consider rearranging the
dir structure to put jsps separate from content,
but that doesn't seem like a useful step at this
time.

Other ideas?

-Paul

We had the same problem with a jsp-property-group url-pattern, and I did
some searches on google on this topic (that's how I ended up in here for
example)

Most clear result I found was:

http://www.mail-archive.com/tomcat-d.../msg43676.html

Where it says that mapping /somepath/*.something worked in a version of
tomcat, but is removed since it does not comply with the Servlet
specification.

This is what the servlet specification (2.4) allows:

- A string beginning with a / character and ending with a /* suffix is
used for path mapping.
- A string beginning with a *. prefix is used as an extension mapping.
- A string containing only the / character indicates the "default" servlet
of the application. In this case the servlet path is the request URI minus
the context path and the path info is null.
- All other strings are used for exact matches only.


So what you (and we) are trying to do, cannot be done according to the
Servlet 2.4 specification.