Topic: [Solved] Problem with proxy and Output filters

[hbbk]

hi

I've an apacher server (Apache/2.2.22 (Debian)) wich goal is to proxy application server (tomcat).
Mainly https://apache/service proxy to http://tomcat:8080/

My problem is that the tomcat service hard write links in its results (http://tomcat:8080/result) so I put in place an external output filter to change all links in results to something usable by users. As the tomcat seems to outpuy gzipped content I added an inflate filter in the chain.

[maba]

Hello,

while it might be possible to do these things using a zillion of Apache modules, it is typically not a good idea.

With Apache and a backend Tomcat an old golden IT rule still applies: "keep it simple".

So what I would do in such a situation is to map the Tomcat WebApp context one by one. Example: lets assume you have a jenkins behind your Apache then you instruct Tomcat to use the context path /jenkins. The Tomcat container will then work relative to that.

URL: http://localhost:8080/jenkins

On the Apache side, you would just match that

[hbbk]

thanks maba for your reply
but that's exactly what I do actually , I didn't put that in my previous message but everything is in a <Location> directive

the pb is that the tomcat application - this is alfresco - does hard write absolute links in it's code, with javascript, so somewhere inside the page there is somthing like

[glsmith]

Have you looked at mod_proxy_html?

[hbbk]