You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Chris Taylor <ch...@phi-web.co.uk> on 2002/08/01 04:31:06 UTC
Proxied backend webserver problem
Hi,
I am having difficulty getting the "Parent Directory" links on my
mod_autoindex'd dirs working correctly.
The situation is that I have http://server1/ and then a second server mapped
into it's FS on http://server1/server2 using the mod_proxy features. The
problem is that autoindexed directories on server2 are now pointing to / as
their "Parent Directory" link, because the server does not realise it has
been mapped in as /server2/.
I have tried setting server2's ServerName to server1/server2 (ie: the
directory) but this does not work.
Any ideas?
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Proxied backend webserver problem
Posted by Chris Taylor <ch...@phi-web.co.uk>.
Thanks for the prompt response, that was exactly what I was looking for :)
Cheers.
Chris Taylor - chris@phi-web.co.uk - The guy with the PS2 Webserver :)
----- Original Message -----
From: "Daniel Lopez" <da...@rawbyte.com>
To: <us...@httpd.apache.org>
Sent: Thursday, August 01, 2002 3:48 AM
Subject: Re: Proxied backend webserver problem
>
>
> > Hi,
> >
> > I am having difficulty getting the "Parent Directory" links on my
> > mod_autoindex'd dirs working correctly.
> >
> > The situation is that I have http://server1/ and then a second server
mapped
> > into it's FS on http://server1/server2 using the mod_proxy features. The
> > problem is that autoindexed directories on server2 are now pointing to /
as
> > their "Parent Directory" link, because the server does not realise it
has
> > been mapped in as /server2/.
> >
> > I have tried setting server2's ServerName to server1/server2 (ie: the
> > directory) but this does not work.
>
> The reverse proxy can replace HTTP headers in the response (such as
> redirects) but does not go and replace the links in the content being
served
> (directory listings in this case)
>
> I suggest you do the following in server2:
>
> alias /path/to/documentroot /server2
>
> And in server1:
>
> ProxyPass /server2 http://server2/server2
>
> That should make the trick
>
> Daniel
>
> --
> Teach Yourself Apache 2 -- http://apacheworld.org/ty24/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Proxied backend webserver problem
Posted by Daniel Lopez <da...@rawbyte.com>.
> Hi,
>
> I am having difficulty getting the "Parent Directory" links on my
> mod_autoindex'd dirs working correctly.
>
> The situation is that I have http://server1/ and then a second server mapped
> into it's FS on http://server1/server2 using the mod_proxy features. The
> problem is that autoindexed directories on server2 are now pointing to / as
> their "Parent Directory" link, because the server does not realise it has
> been mapped in as /server2/.
>
> I have tried setting server2's ServerName to server1/server2 (ie: the
> directory) but this does not work.
The reverse proxy can replace HTTP headers in the response (such as
redirects) but does not go and replace the links in the content being served
(directory listings in this case)
I suggest you do the following in server2:
alias /path/to/documentroot /server2
And in server1:
ProxyPass /server2 http://server2/server2
That should make the trick
Daniel
--
Teach Yourself Apache 2 -- http://apacheworld.org/ty24/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org