Menu

#2 Contradiction in description of (always|never)_direct

open
nobody
None
5
2000-10-17
2000-10-17
Anonymous
No

To me, the following extracts from http://squid-docs.sourceforge.net/latest/html/x2268.htm
sound contradictory;
<<
Squid checks all always_direct tags before it checks any never_direct
tags. If a matching always_direct tag is found, Squid will not check the
never_direct tags, but decides which cache to talk to immediately.
>>
versus
<<
First, let's consider a request destined for the web server
intranet.mydomain.example. Squid first works through all the always_direct
lines; the request is matched by the first (and only) line.
[...]
If the line used the deny keyword instead of allow, Squid would have
simply skipped on to checking the never_direct lines.
>>

When squid finds a matching always_direct, does it
a) ignore all never_direct tags, regardless of allow/deny in the
always_direct, or
b) ignore the never_direct tags if and only if the always_direct is
an allow

Anders Baardsgaard -- <anders@nhn.no>

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.