RE: [squid-users] Squid as an HTTP accelerator (fwd)

I'm just curious to find out what extent rproxy can rewrite URLs without a
redirector...

The application server that I primarily use (Zope, which has a built-in http
server) supports virtual-hosting in a somewhat different way, using
something called a VirtualHostMonster, requiring the path be modified to in
order to have the app server dynamically rewrite environment variables used
to build hyperlinks on pages with the externally-visible URLs. In this
situation, a redirector is still going to be required, if I understand
correctly? Or would Squid-rproxy be able to rewrite a URL like below?

An example of my rewrite rules (from pyredir, the redirector I use):
^http://classifieds.signonsandiego.com[/]?(.*)
=http://nodes.foo.com:9673/myhost/VirtualHostBase/http/myhost.foo.com:80/myh
ost/VirtualHostRoot/\1

In this scenario, Zope runs on port 9673; queries to this get the URLs used
in writing output content as http://myhost.foo.com/ as a base, using the
/myhost folder as a content root.

Sean

-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: Thursday, September 20, 2001 12:30 PM
To: Winfried Truemper
Cc: squid-users@squid-cache.org
Subject: Re: [squid-users] Squid as an HTTP accelerator (fwd)

Good writing. Too sad most will be obsolete in some time (probably
during Squid-2.6).

I'd strongly recommend anyone investigating setting up a complex
accelerator to visit http://squid.sourceforge.net/rproxy/. This is a
complete rework of how to configure Squid as a reverse-proxy and allows
you to create a full featured reverse proxy with a wide varity of
domain/ip/url pattern/user -> backend server mapping possibilities, all
without requiring redirectors.

In Squid-rproxy a redirector/URL rewriter is only required if you need
to change the URL-path before forwarding the request to the correct
backend server.

The basic design is the same as for forward proxying in a cache mesh,
but instead of peering with other caches Squid peers with your backend
servers (well.. you may also peer with other caches if you like)

One non-Squid comment: I did not understand the section on Apache
suexec. A normal suexec setup does not require all users to share the
same account. A setup without suexec does.

--
Henrik Nordstrom
Squid Hacker
Winfried Truemper wrote:
> 
> Hi,
> 
> it quite did cost me some time to fiddle out all the details of using
> Squid as an HTTP accelerator. I thought I would let you share:
> 
> http://wt.xpilot.org/projects/squid/http_accel/setup.txt
> 
> Regards
> -Winfried