Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 7104 invoked by uid 500); 23 Oct 2002 16:38:43 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 7093 invoked from network); 23 Oct 2002 16:38:43 -0000 Received: from mail15.messagelabs.com (63.210.62.243) by daedalus.apache.org with SMTP; 23 Oct 2002 16:38:43 -0000 X-VirusChecked: Checked Received: (qmail 24079 invoked from network); 23 Oct 2002 16:38:09 -0000 Received: from dcimail.donaldson.com (162.107.240.195) by server-30.tower-15.messagelabs.com with SMTP; 23 Oct 2002 16:38:09 -0000 Received: by dcimail.donaldson.com with Internet Mail Service (5.5.2653.19) id ; Wed, 23 Oct 2002 11:41:56 -0500 Message-ID: <11864A3328DDD5119DE70002A540D64A02B4BFA0@ntblm16.dci.com> From: "Nelson, Robert D." To: "'users@httpd.apache.org'" Date: Wed, 23 Oct 2002 11:38:22 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: RE: [users@httpd] Reverse proxy + redirect problem Mike: > 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 http://revproxyname/alias/somepage.html ...expected... > 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 http://revproxyname/alias/somepage.html. ...expected... > 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 http://httpd.apache.org/docs/ ~ Robert --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org