Re: [squid-users] Cache_peer config

On 28/11/2012 1:48 a.m., 金 戈 wrote:
> This is my configure, and we use squid mutli-instance. 2 squid2.7 as frontend, and 3 squid2.7 as backend.And it's load-balanced.
>
> cache_peer ip1 parent 3128 0 carp no-netdb-exchange no-digest no-query login=PASS no-tproxy name=backend1a http11
> cache_peer ip2 parent 3128 0 carp no-netdb-exchange no-digest no-query login=PASS no-tproxy name=backend1b http11
> cache_peer ip3 parent 3128 0 carp no-netdb-exchange no-digest no-query login=PASS no-tproxy name=backend1c http11

If you want HTTP/1.1 features you are better off upgrading to Squid-3.2
than using the experimental features in 2.7. Yes they work well, but are
incomplete and 3.2 contains a lot of additional feature support
(including SMP support).

"no-tproxy" is a Squid-3.1 feature. Plus squid-2.7 does not support
TPROXYv4 which is embeded in modern (2.30+) Linux kernels.

Amos
Received on Wed Nov 28 2012 - 06:15:10 MST