RE: [squid-users] Configuring reverse proxy

1. Squid will round robin a single back-end requested URL to multiple boxes
if DNS resolves more than one IP name for that name. With Squid 2.4 if you
compiled with --disable-internal-dns, you could use the external dnsserver
program and make multiple entries in /etc/hosts for the same name. Squid
will round-robin between these. I think, though I am not sure, that Squid
2.5 eliminates the need to compile this way to support use of /etc/hosts,
but I am not sure. If you are using comfortable using DNS with multiple A
records for the same name, then go ahead and do that instead (it will scale
better anyways).

2. In some very limited cases, Squid can do true load-balancing, but only if
your application server supports ICP as well as HTTP (you effectively make
your app servers nodes part of the cache hierarchy, tricking Squid to behave
as if they were, Squid balances ICP stuff more intelligently than a simple
round-robin); Zope is the only app server I know of that does this.

3. A redirector can act to redirect one front-end URL to other URLs based on
some criteria, like client IP, or URL regex. This is useful to give Squid
the power to support different portions/paths/urls on the same hostname on
multiple, logically separate server pools. It also allows you to avoid
forwarding loops by making the back-end hostname(s) different than the
hostname public/authoritative DNS servers use for your public URL (which, of
course, resolves to your cache's external, public IP). If you need a
redirector that is flexible, and easily modifiable, I would suggest Pyredir,
written in Python with an easy to use configuration file
(http://freshmeat.net/projects/pyredir).

Sean

-----Original Message-----
From: Brian F. Vaughan [mailto:bvaughan@wgen.net]
Sent: Wednesday, December 18, 2002 8:24 AM
To: squid-users@squid-cache.org
Subject: [squid-users] Configuring reverse proxy

Hello all,

I've perusing the squid docs and white papers and have not found a way to
reverse proxy multiple backend servers for a single domain.

I.e. domain: foo.com ---> Some public IP

          Backend web servers for foo.com
                        web1 (10.x.x.x) web2 (10.x.x.x) web3 (10.x.x.x)

The closet the docs came to something like this was reverse-proxy of
multiple domains, I just want to reverse proxy a single domain with multiple
backend servers. Any ideas?

Sincerely,

Brian Vaughan.
Received on Wed Dec 18 2002 - 11:01:46 MST