Equivalent of Apache's ProxyPassReverse?

From: Michael Smith <mjs@dont-contact.us>
Date: Sat, 17 Oct 1998 13:25:46 +0100

Apologies if this comes up a lot, I couldn't find any obvious references
in the archive. In the FAQ, section 20.3:

--
20.3 When using an httpd-accelerator, the port number for redirects is
wrong
Yes, this is because you probably moved your real httpd to port 81. When
your httpd issues a redirect message (e.g. 302 Moved Temporarily), it
knows it is not running on the standard port (80), so it inserts :81 in
the redirected URL. Then, when the client requests the redirected URL,
it
bypasses the accelerator.
--
Apache can use a different mechanism to counteract this, namely
ProxyPassReverse:
http://www.apache.org/docs/mod/mod_proxy.html#proxypassreverse
--
This directive lets Apache adjust the URL in the Location header on HTTP
redirect responses. For instance this is essential when Apache is
used as a reverse proxy to avoid by-passing the reverse proxy because of
HTTP redirects on the backend servers which stay behind the reverse
proxy.
--
I find this option preferable to that suggested in the Squid FAQ, so I
was wondering if there is any way of getting Squid to do what
ProxyPassReverse does?
Thanks
Michael Smith
Received on Sat Oct 17 1998 - 07:15:03 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:42:32 MST