On 22.05.2009 04:31, Andre-John Mas wrote:
On 21-May-2009, at 12:32, Rainer Jung wrote:
On 20.05.2009 17:33, Markus Schönhaber wrote:
Andre-John Mas:
this is not the ideal setup, I don't have any control over this. At
the same time I see that using mod_proxy, by way of ProxyPass, means
On 20.05.2009 17:33, Markus Schönhaber wrote:
Andre-John Mas:
this is not the ideal setup, I don't have any control over this. At
the same time I see that using mod_proxy, by way of ProxyPass, means
that the Tomcat server does not know what hostname was used to access
the Apache
On 21-May-2009, at 12:32, Rainer Jung wrote:
On 20.05.2009 17:33, Markus Schönhaber wrote:
Andre-John Mas:
this is not the ideal setup, I don't have any control over this. At
the same time I see that using mod_proxy, by way of ProxyPass, means
that the Tomcat server does not know what
Hi,
Where I work the production environment is using Apache HTTPD in front
of Tomcat and the link is then made via mod_proxy. While I understand
this is not the ideal setup, I don't have any control over this. At
the same time I see that using mod_proxy, by way of ProxyPass, means
that
From: Andre-John Mas [mailto:aj...@sympatico.ca]
Subject: mod_proxy, Tomcat and request URL
At the same time I see that using mod_proxy, by way of ProxyPass,
means that the Tomcat server does not know what hostname was used
to access the Apache server, instead getting http://localhost:8080
Andre-John Mas:
this is not the ideal setup, I don't have any control over this. At
the same time I see that using mod_proxy, by way of ProxyPass, means
that the Tomcat server does not know what hostname was used to access
the Apache server, instead getting http://localhost:8080/ . Is