Search squid archive

Re: Connect directly if parent cache fails

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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  8080            0       no-query
no-digest default connect-fail-limit=5
prefer_direct off
never_direct allow all


But squid will never connect directly, even if the parent isn't
available. How can I implement this?


WTF? (sorry but you will kick yourself in a second)

You have set a directive called "never_direct" to always be true/on/working and are having trouble because Squid never connects directly.


So, you need to drop that never_direct entry.
Also drop any hierarchy_stoplist entries.

Also take a look at nonhierarchical_direct, it operates on requests like CONNECT which are best handled directly. Setting it to ON will make the peer handle those as well when its available.

Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.11
  Beta testers wanted for 3.2.0.5


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux