Thanks Mark.
I'll try to upgrade to the latest then.
Invoker: I know it is bad (even more than the overlord), probably don't know
how bad or the impact it has in usage, but for now it works.
I've read some about it, but never could really understand the problems it
brings.
In our current situation, mapping the servlets is a bit messy, probably
because our developing process is messy...
Thanks again Mark.
Regards,
Federico.
-----Mensaje original-----
De: Mark Thomas [mailto:ma...@apache.org]
Enviado el: miércoles, 08 de junio de 2011 11:35
Para: Tomcat Users List
Asunto: Re: Static resource mapping in web.xml
On 08/06/2011 15:17, falva...@geocom.com.uy wrote:
> I have a WEBAPP which uses the "invoker" servlet (i know
how
> bad it is, but for now it gets the job done).
That is such a monumentally bad idea I'm not at all sure you really do
understand just how bad it is.
> The problem is that static content is not shown under
> "images", it is shown under "images/images".
That is because the default servlet was designed and documented only for
mapping to /*
Since so many people mis-use it (which creates security issues) support
for mapping to something other than /* was added in 6.0.30 onwards.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
