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 hostname was used to
access
the Apache server, instead getting http://localhost:8080/ . Is there
any way, probably via configuration of Apache, that this could be
passed to the Tomcat? I looked for information on this, but I could
not find any.
Instead of mod_proxy_http, I use mod_proxy_ajp. AJP passes the
client's
IP through.
On 20.05.2009 16:59, Caldarale, Charles R wrote:
Aren't the X-Forwarded-For and X-Forwarded-Host headers being set by
mod_proxy? The doc indicates they should be:
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html
.. and finally there's ProxyPreserveHost.
That's one option I missed.
Is there any way to know whether Apache was contacted using HTTPS or
HTTP, on the Tomcat side?
If yo want to get an idea, which other traps are to avoid when using a
reverse proxy, you can also look at
http://tomcat.apache.org/connectors-doc/generic_howto/proxy.html
I would love to go with AJP, but due to a very conservative customer,
this is not an option we can look at. The other points on the page
with regards to URL rewriting seem of interest, though the idea is
to try to remove assumptions to what name the client is accessing
the host by. The reason is so when we move from dev to integration
to production, this is one less thing to keep track of.
André-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
