rproxy is obviously the path to go as you mention yourself. If too
much of a hassle then consider trying out a eMARA from MARA Systems
(email info@marasystem.com if interested). If you only want the
location rewrite feature of the patch then this is farily well
isolated, but you may need to dig around a little to fin the correct
place where to slot it into the reply processing.
The rproxy patch is actually reasonably up to date, it is only that
certain features do not work when the HEAD version is used
(specifically the error_map directive). If you are unsure about which
version to apply the patch to then grab the whole source tree via
CVS. Or just give it some time and gradually more and more of the
features from rproxy will appear in HEAD. Currently waiting for other
possibly conflicting changes that are scheduled to go in first before
spending more time on the HEAD version of rproxy.
Also, we (MARA Systems AB) do have a Squid-2.5 version of the rproxy
patch available to eMARA customers who ask for it.
Regards
Henrik
On Wednesday 04 September 2002 21.59, Ricardo Kustner wrote:
> Anyway I think it would be a very valuable addition to using squid
> as a reverse proxy if it could rewrite the Location headers so any
> backend apps which do redirects based on their servername and port
> can be correctly reverse proxied... (aka ProxyPassReverse in Apache
> mod_proxy) I know the rproxy patch does exactly this, but beside it
> being out of sync with the source at the moment; it does a lot more
> than that... I studied the patch a bit and it looks as not an easy
> task to filter it out (especially since it's hard to find the
> correct version of the source to patch it against)
> so any ideas on how to get squid to support this as easily as
> possible?
>
> TIA...
>
> Regards,
>
> Ricardo.
Received on Wed Sep 04 2002 - 15:05:35 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:10:05 MST