Re: Rewrite relative image paths in a reversed proxy setup

[Bocalinda <bocalinda@xxxxxxxxx>]

Hey Nick.

http://172.18.0.39:8080 is the URL of one of my Tomcat servers.
Not my load balancer. That's what I mean with hardcoded.
I cannot put the URL of the load balancer, as I have 2 Tomcat clusters
being served by the same load balancer. Each cluster runs a different application.
The load balancer does not know to which application the requested image belongs, 
and thus cannot forward the request to the apropriate cluster.
I don't know if this is what you meant?

2008/11/18 Nick Kew <nick@xxxxxxxxxxxx>

On Mon, 17 Nov 2008 13:38:21 +0100
Bocalinda <bocalinda@xxxxxxxxx> wrote:

> <Location /SEDO>
>        ProxyPass balancer://mycluster1 stickysession=JSESSIONID
>        ProxyPassReverse /
>        SetOutputFilter proxy-html
>        ProxyHTMLURLMap (.*\.gif) http://172.18.0.39:8080/$1 Rie
> </Location>
>
> This works, however, what I do not like is that I map the URLs to a
> hardcoded server. What if the Tomcat instance is down? Then my images
> won't be loaded.

Where's the hardcoded server in that?  The reverse proxy's role
is to map *away from* any hardcoded paths, *into* an address -
often a relative one - that resolves to the proxy.

The above looks wrong to me.


--
Nick Kew

Application Development with Apache - the Apache Modules Book
http://www.apachetutor.org/

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx