On 23/08/2009 12:23, André Warnier wrote:
Gerardo Corro wrote:
Hi,
I have 6 different web-apps (let's call their contexts /wa1, /wa2 ...
/wa6) running in port 8080.
I have another web-app named /proxy running on port 80. As the name
suggests this web-app does proxy functions for the other 6 web-apps.
This proxy basically is meant to go to any of the web-apps and follow
any number of redirects until a final page is reached, so external
clients always get the needed resource in one shot.
For instance, a client requests: http://hostname:80/wa1/resourcex,
then the request should actually go to http://hostname:80/proxy, after
that the proxy makes all calls following redirects to
http://hostname:8080/wa/resourcex (where the actual web-app context
runs) and returns the final result to the client.
That seems (to me) a quite complicated setup for something that looks
essentially like URL rewriting.
Have you looked at the urlrewrite filter ?
http://www.tuckey.org/urlrewrite/
Or worse, an attempt to obfuscate the true URLs in a peculiar and
ill-advised attempt to improve security.
p
---------------------------------------------------------------------
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
