Apache with mod_proxy + mod_jk = total confusion ?
We're experiencing a rather strange problem with one of our web application at the moment.
The said application is running on Tomcat and located behind firewall. On the webserver, we have a second instance of Apache loaded with mod_jk to connect to that Tomcat box.
Incoming requests to www.website.com/application is forwarded by the main instance of Apache to the second instance, using mod_proxy.
Everything is running well, until... when a user is browsing our website using its ISP's proxy.
Then instead of getting http://www.website.com/application back from the server, the page they're getting back have the links in it pointing to http://<internal_IP_address>/application
Pretty nasty.
We've checked the logs, but there's no clue as to why this problem happens.
I think the header got messed up somehow when mod_proxy received a request from another proxy (in this case, ISP's proxy).
But of course we can't ask the users to disable their proxy (as some proxy is transparent to users), and we can't put mod_jk in the main Apache instance due to conflict with Websphere's apache module...
Anyone experienced similar problem ? Please let me know.
Many thanks,
Harry
