tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From LERBSCHER Jean-Pierre <>
Subject RE : Tomcat vs Apache
Date Thu, 19 May 2005 15:00:47 GMT
See comment in message.

-----Message d'origine-----
De : Tim Diggins [] 
Envoyé : jeudi 19 mai 2005 13:24
À : Tomcat Users List
Objet : Re: Tomcat vs Apache

(Er, and sorry I just realised I posted __some__ of this as part of a 
question on the list last week, but the question I have is now posed 
more concretely and wasn't answered then)!

Tim Diggins wrote:
> This has been a great and informative thread... I'm wondering now, how 
> to accomplish what I want to do in Tomcat alone, rather than looking for 
> a Tomcat+Apache solution (sounds simpler).
> The issue is that I want ALL directory-like urls resolved by a 
> particular servlet (which is a Spring dispatcher servlet, but never mind 
> that), but I would like very few kinds of static files (which I could 
> name explictly *.gif, *.png, *.css or put under a static place) served 
> statically (ie by the "default" servlet.
> The problem is that the url-pattern for a directory-like urls covers all 
> urls.
> Is there a way to do the reverse of normal, state that you want  a 
> particular url-pattern (e.g. "/static/*") to go to the "default servlet" 
> , and everything else (e.g. "/*") to go to a particular servlet. If so, 
> how do I indicate the "default servlet" in my web.xml?
SRV.11.2 Specification of Mappings
In the web application deployment descriptor, the following syntax is used
to define mappings:
* A string beginning with a '/' character and ending with a '/*' postfix 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 pth and the path info is null.
* All other strings are used for exact matches only.
> (And I've already had recommendations from people to change the URLs for 
> the dynamic stuff to something else, but that's not what the 
> client/customer/user/design wants -- the url is very much part of the 
> user interface in this application).
> thanks
> Tim


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message