[squid-users] Connect directly if parent cache fails

2011-02-17 Thread Tom Tux
Hi I'm trying to configure Squid (3.1.9) to connect directly, if the one and only cache_peer (parent) fails: cache_peer xx.xx.xx.xx parent 80800 no-query no-digest default connect-fail-limit=5 prefer_direct off never_direct allow all But squid will never connect directly, eve

Re: [squid-users] Connect directly if parent cache fails

2011-02-17 Thread Amos Jeffries
On 17/02/11 21:29, Tom Tux wrote: Hi I'm trying to configure Squid (3.1.9) to connect directly, if the one and only cache_peer (parent) fails: cache_peer xx.xx.xx.xx parent 80800 no-query no-digest default connect-fail-limit=5 prefer_direct off never_direct allow all But sq

Re: [squid-users] Connect directly if parent cache fails

2011-02-20 Thread Tom Tux
Hi Is my scenario in general possible to implement (connect directly, if the one and only cache_peer fails)? Thanks a lot. Tom 2011/2/17 Tom Tux : > Hi Amos > > This doesn't work as expected. I removed the "never_direct" entry (I > was unsure, how "strong" it is in the configuration...) and drop

Re: [squid-users] Connect directly if parent cache fails

2011-02-20 Thread 叶雨飞
Hi there, I've been trying to do the same thing, but squid always tries too hard on parents. You can do this as what I do: Have a local squid with "always_direct allow all" listening on another port as the last entry of cache_peer with a default . when squid tried the peers above and failed, it

Re: [squid-users] Connect directly if parent cache fails

2011-02-21 Thread Amos Jeffries
On 21/02/11 20:27, Yucong Sun (叶雨飞) wrote: Hi there, I've been trying to do the same thing, but squid always tries too hard on parents. You can do this as what I do: Have a local squid with "always_direct allow all" listening on another port as the last entry of cache_peer with a default . wh