On Sun, 17 Nov 2002, Reynir Hübner wrote:
> Date: Sun, 17 Nov 2002 10:53:20 -0000 > From: Reynir Hübner <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: RE: Servlet filter mapping > > > Thanx craig. > > I wonder why this is not a part of the spec, as it could be very usefull. > If you map your filter to "/*", it can already make whatever dynamic decisions it wants to about dealing with the request. Therefore, it doesn't really need to be in the container. > Is there a way of setting the url-patterns on runtime, or only in web.xml ? The only standard mechanism is to create the patterns in web.xml. > > Thanx again, > -reynir Craig > > > > > > > There are only four standard URL patterns (and this applies > > to servlet mappings and security constraints as well as > > filter mappings): > > > > * Exact match (/foo) > > * Path match (/foo/*) > > * Extension match (*.foo) > > * Default servlet (/) which is useful only for servlet mappings > > > > There is no legal syntax to say "all but this set of paths". > > > > Craig > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
