On 26.08.2009 00:20, Troy Bull wrote:
Greetings
I have been trying to get this to work for hours and I am stuck. I
am trying to configure mod_jk and it works to a point, that is up
until the back end app does a redirect, the redirected url is passed
all the way back to the browser, then the browser goes directly
against the app server bypassing my apache and mod_jk. Is there a
way to make mod_jk fix this redirected url so that is gets pointed
back at my proxy server?
Any help greatly appreciated Thanks troy
Unfortunately the answer is: mod_jk uses the AJP13 protocol, which is a
good way to fix this. More precisely: AJP13 ensures, that the web
container provides the Apache port, protocol and server name to the
webapp, if it asks about this data to produce a self referring URL.
If you use http between Apache and Tomcat instead, you need to set
additional attributes on the Tomcat connector to fix the data.
So I would say your webapp is broken, in that it asumes standard data
instead of using the servlet API to ask the container for the needed
data. Maybe there's a config item for your webapp.
Nevertheless you can play tricks, because the redirects are done using a
response header called Location, which you can rewrite using mod_headers.
Have a look at
http://tomcat.apache.org/connectors-doc/generic_howto/proxy.html
and search for Location, but do also read the rest of the page.
Regards,
Rainer
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org