Re: Avoid duplicate peers for no-direct and maybe-direct forwarding

2012-05-09 Thread Amos Jeffries
On 10.05.2012 04:14, Alex Rousskov wrote: On 04/28/2012 10:50 PM, Alex Rousskov wrote: 2. Change lower-level peerAddFwdServer() so that only new servers are added even if the higher level code tries to add duplicates; the "same server" comparison can be done using server address (including

Re: Avoid duplicate peers for no-direct and maybe-direct forwarding

2012-05-09 Thread Henrik Nordström
ons 2012-05-09 klockan 10:14 -0600 skrev Alex Rousskov: > FWIW, the "duplicate peer addresses" problem does not exist in Squid 2.7 > which indirectly supports my assumption that this is a bug rather than a > feature. Squid-2 peerAddFwdServer skips duplicate peers. while (*FS) { if ((

Re: Avoid duplicate peers for no-direct and maybe-direct forwarding

2012-05-09 Thread Alex Rousskov
On 04/28/2012 10:50 PM, Alex Rousskov wrote: > Hello, > > While trying to configure Squid to resend the request to the second > cache_peer if the first one fails, I noticed that the first peer is > tried twice: > > # this peer will be tried twice in a row: > cache_peer 172.16.101.151 pare

Avoid duplicate peers for no-direct and maybe-direct forwarding

2012-04-28 Thread Alex Rousskov
Hello, While trying to configure Squid to resend the request to the second cache_peer if the first one fails, I noticed that the first peer is tried twice: # this peer will be tried twice in a row: cache_peer 172.16.101.151 parent 80 0 originserver no-query # then this peer will be tri