Hi All, I'm in the process of upgrading some clients to the latest squid proxy version. Coming from version 3.5 I used to specify backends in squid.conf as follows; cache_peer site1.domain.com parent 443 0 no-query originserver name=server_site1 ssl proxy-only front-end-https=on login=PASS cache_peer_domain server_site1 site1.domain.com cache_peer site2.domain.com parent 443 0 no-query originserver name=server_site2 ssl proxy-only front-end-https=on login=PASS cache_peer_domain server_site2 site2.domain.com But in Squid 4 it looks a little confusing, cache_peer_domain is superseded by cache_peer_access but looking at the documentation it looks like cache_peer_access isn't quite the same as cache_peer_domain. So I ended up looking neighbour_type_domain which looks like what I want, so I've configured as following; cache_peer site1.domain.com parent 443 0 no-query originserver name=server_site1 login=PASS ssl front-end-https=on neighbor_type_domain server_site1 site1.domain.com cache_peer site2.domain.com parent 443 0 no-query originserver name=server_site2 login=PASS ssl front-end-https=on neighbor_type_domain server_site2 site2.fotechsolutions.com Which seems ok, but what I end up seeing is site1.domain.com is proxied correctly, but when browsing for site2.domain.com I end up loading site1.domain.com, am I missing something in this new version? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-4-0-18-question-about-directives-tp4681599.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
