Re: prefer_direct question

Hi Patrick (and others)

I experienced exactly the same thing this afternoon, after upgrading to the
devel 3 release and experimenting with some of the settings. Perhaps a
slightly better choice of words would help the problem - prefer_direct
implies that it's a preference and therefore can be overruled. As far as I
can tell, the most obvious setting which should override prefer_direct
should be always_direct - but always_direct does nothing when prefer_direct
is set to off.

How about force_cache_peer rather than prefer_direct for words? Or better
still, allow always_direct to override prefer_direct?

Reuben

In article <7amn3t$36m$1@FreeBSD.csie.NCTU.edu.tw>,
  patrick@oscar.prima.de (Patrick Mau) wrote:
>
> Hallo list-members,
>
> I'm using squid-2.2.DEVEL3 and have a small question about
> prefer_direct. Because of our firewall setup I'm unable to fetch
> directly from origin servers, but I still want to go direct to servers
> inside our firewall.
>
> I have something like this in my squid.conf:
>
> acl local_servers dst 1.2.3.0/24
> always_direct allow local_servers
>
> When I set 'prefer_direct off', the above 'always_direct' will no
> longer work. Everything is fine when I change it to 'on'.
>
> It seems to me that 'always_direct' is completly ignored when
> 'prefer_direct' is not set.
>
> Is it intentional that 'prefer_direct' changes the semantics of
> 'always_direct' and 'never_direct' ?
>
> thanks,
> Patrick
>
>
Received on Sun Feb 28 1999 - 03:14:14 MST