[squid-users] Proper Cache Peer Access

[creditu at eml.cc]

Looking for the best way to provide cache peer access for two urls on a
3.1 accelerator.  For example if a set of backend servers fullfill
requests for both www.example.com and www-legacy.example.com is the
following the correct way to handle them in regards to the cach peer
access? 


http_port 192.168.100.1:80 accel defaultsite=www.example.com vhost
http_port 192.168.100.2:80 accel defaultsite=dev.example.com vhost

https_port 192.168.100.1:443 accel defaultsite=www.example.com vhost
cert=/path/cert.pem key=/path/key.pem
https_port 192.168.100.2:443 accel defaultsite=dev.example.com vhost
cert=/path/cert.pem key=/path/key.pem

# Backend servers for www and www-legacy
acl www dstdomain www.example.com
acl www-legacy dstdomain www-legacy.example.com
cache_peer 10.10.10.1 parent 80 0 no-query no-digest originserver
round-robin
cache_peer_access 10.10.10.1 allow www
cache_peer_access 10.10.10.1 allow www-legacy
cache_peer_access 10.10.10.1 deny all

cache_peer 10.10.10.2 parent 80 0 no-query no-digest originserver
round-robin
cache_peer_access 10.10.10.2 allow www
cache_peer_access 10.10.10.2 allow www-legacy
cache_peer_access 10.10.10.2 deny all

# Backend server for dev
acl dev dstdomain dev.example.com
cache_peer 10.10.10.3 parent 80 0 no-query no-digest originserver
round-robin
cache_peer_access 10.10.10.3 allow dev
cache_peer_access 10.10.10.3 deny all