httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Finn, Michael" <>
Subject RE: [users@httpd] Reverse proxy + redirect problem
Date Wed, 23 Oct 2002 17:10:33 GMT
I am confused - I thought the HTTP header location field is what drives what
the browser uses (and what shows up in the URL in the browser), which is why
ProxyPassReverse sets it for redirects (according to the docs). BTW - I
don't care about Rev Proxy adjusting links within the content - there are no
absolute links there anyway.


-----Original Message-----
From: Nelson, Robert D. []
Sent: Wednesday, October 23, 2002 12:38 PM
To: ''
Subject: RE: [users@httpd] Reverse proxy + redirect problem


> Using mod_proxy. Config'd like so in httpd.conf 
>   ProxyPass /alias http://some-host/real-app 
>   ProxyPassReverse /alias http://some-host/real-app 

That looks right...

> When real-app is serving a page that does not issue redirect, everything
is cool. The URL comes back to the browser as


> But, when a redirect IS issued, the URL does not get adjusted by
ProxyPassReverse, and the browser gets a URL like
http://some-host/real-app/somepage.html, instead of


> For us, revproxy is a DMZ box, and some-host is on our private LAN. So,
the user gets a URL that won't even resolve on the 'net.
> I thought rewriting the URL for redirects was the sole purpose of
ProxyPassReverse. Is it not?

Not entirely.  ProxyPassReverse will change the URL in the Location part of
the HTTP header.  It *will not* parse through your pages to adjust links,
meta refreshes, etc.

> This behavior is consistent on 1.3.x and 2.0.x, so I am guessing I am
doing something wrong. 

I don't think you're doing anything wrong, you just have the wrong
expectations.  Take a look at the documentation at

 ~ Robert

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