RE: [squid-users] bungling my squid.conf for front-end-https=on, OWA

I'm having a bit of trouble putting it all together. I seem to be able to get 1 cache_peer working ok without using cache_peer access and acls, but getting two to work is proving difficult. Here are the relevant config lines:

httpd_accel_host virtual
httpd_accel_port 0
httpd_accel_uses_host_header off
cache_peer host1.mydomain.com parent 80 443 no-query front-end-https=on
cache_peer host2.mydomain.com parent 80 443 no-query front-end-https=on

never_direct allow all

acl owa dst [ip host1]/255.255.255.255
cache_peer_access host1.mydomain.com allow owa
cache_peer_access host1.mydomain.com deny all

acl web dst [ip host2]/255.255.255.255
cache_peer_access host2.mydomain.com allow web
cache_peer_access host2.mydomain.com deny all

If I take out the acls, host 1 works. With this config, neither host works. Any help would be appreciated.

thanx,

David

-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: Wed 8/13/2003 5:31 PM
To: David Gibson; squid-users@squid-cache.org
Cc:
Subject: Re: [squid-users] bungling my squid.conf for front-end-https=on, OWA
On Wednesday 13 August 2003 22.54, David Gibson wrote:
> Looks like squid doesn't like the virtual port in this version.

Sorry, the syntax is

httpd_accel_port 0

(see the squid.conf documentaiton).

> Can you still have squid redirect to more than one server? If so,
> how?

You can select which physical server the request gets forwarded to by
using cache_peer_access.

> Is there a cache_peer virtual?

Each cache_peer support any number of domains, or to be precise as
many as the server it connect to supports.

If you have more than one server and different domains on different
servers then you need to use cache_peer_access to tell Squid which
cache_peer it should use for which request.

Regards
Henrik
Received on Mon Aug 18 2003 - 13:12:12 MDT