RE: [squid-users] Multiple httpd-accelerated servers in squid v.3

Is there an example, for squid pre 3, that shows this?

For example: 10.87.10.1 is one back end webserver and 10.87.10.2 is a
second back end webserver.
You desire to have people visit mysite.com/web1 and mysite.com/web2 to reach
those origin servers.

Using regex and a matching directory on the origin servers (all content is
in 10.87.10.1/web1 on one server and all content is in 10.87.10.2/web2 on
the other server) it is simple to do a regex match. What if you wanted to
point to the root of the servers though and have mysite.com/web1 just point
to 10.87.10.2 and return addresses to the browser like
10.87.10.1/web1/files/goodstuff/index.htm when going to the actual server
directly that address would be 10.87.10.1/files/goodstuff/index.htm

Is a redirector needed for this?

For the first example...if all content is in a subfolder of web1, then this
works:

Cache_peer 10.87.10.1 parent 80 0 originserver no-query no-digest proxy-only
login=PASS front-end-https

Acl web1_host urlpath_regex ^/web1
Cache_peer_access 10.87.10.1 allow web1_host
Cache_peer_access 10.87.10.1 deny all

If both 10.87.10.1/images and 10.87.10.1/images exist how can I map web1 and
web2 to end up on the respective servers so it looks like
10.87.10.1/web1/images to the end user?

Hopefully this didn't violate the rule of adding questions to existing
threads, as it appears to be something francois is looking to do as well.

Chris

-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: Wednesday, December 15, 2004 7:10 AM
To: francois visser
Cc: squid-users@squid-cache.org
Subject: Re: [squid-users] Multiple httpd-accelerated servers in squid v.3

On Wed, 15 Dec 2004, francois visser wrote:

> My problem is this: I need to add more web servers to my squid.conf,
> ie. I want clients to reach both https://new-server.my-company.com,
> and https://exchange.my-company.com via the same reverse proxy. What
> do I need to change/add to my current squid.conf? This case is well
> documented for version 2.x, but the mentioned 2 lines are quite
> different from anything I've seen in v. 2.x.

You need additional sets of https_port and cache_peer directives. In
addition you also need cache_peer_access directives telling what requests
should be sent to which web server.

Regards
Henrik
Received on Wed Dec 15 2004 - 06:28:39 MST