httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier>
Subject Re: [users@httpd] Rewrite relative image paths in a reversed proxy setup
Date Mon, 17 Nov 2008 16:25:03 GMT
Bocalinda wrote:
> Hi André.
>>> Applying what you explained above, this would mean that my images paths
>>> will
>>> be resolved as:
>>> Which of course will not work.
>> Why "of course" ?
>> I may be thick, but I must admit I do not really understand your problem.
> Sorry for the confusion, the above image.gif URL wasn't correct.
> If the image path is relative in the form of "image.gif" then the correct
> path would be:
> http://172,18.0.1/image.gif and this of course will not work. (see below)
>> What I mean is : if the page your browser sees contains a tag <img
>> href="image.gif">, the browser will resolve this according to the location
>> from which it got the page that contains that link.
>> That's how browsers work, and are supposed to work.
>> If you do not want this, then do not put relative links in the pages, put
>> absolute links.
>> Like <img href="/images/image.gif">.
>> The browser, mind you, will still resolve this according to the host from
>> which it got your page, but this time will look for
>> But what do you want to happen, really ?
>> Where would you like the image to come from ?
> Hmm, ok. Let me explain what I think is going wrong.
> I request http://172,18.0.1/SEDO.
> As you can see in my Apache configuration, the SEDO location requests will
> be proxied to Tomcat cluster1.
> Let's say that the request will be send to Bear in mind that
> the URL in my browser won't change. That's the whole idea behind a reverse
> proxy. For the client it seems that Apache is serving my pages, while in
> reality it's one of my Tomcat servers in my cluster. Thus, my browser URL is
> still
> Anyway, as you stated, any relative img paths will be resolved to
> But (and this is where the problem is located), this URL will not be proxied
> to any of my Tomcat clusters, because the URL does not contain SEDO or

Sorry, maybe I did not use the correct example before, but that is wrong.
If you original request is
and from there, your browser receives an html page (wherever it came 
from), and that html page contains a link <img href="image.gif">, then 
the browser will request

wait a minute.. maybe it won't. Because it would remove the "SEDO", for 
being the last path component, and replace it by "image.gif".
Now I think I get it.
The browser would have to know that it is not really getting "SEDO", but 

I guess that the only way to make this work (if you cannot change the 
<img> links in the pages), would be to force a re-direct to the real 
thing, when the browser requests "SEDO".

What is the resource that the browser really obtains when it requests
http://172,18.0.1/SEDO ?
(this must be something on your Tomcats)

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message