What to cache
In this example, Caching would not take place for users mary or bob. Note they
are in the same filter!
Qbik recommend reading the advanced
AND: If things are AND
OR: If things are OR
NOT: If a criterion is subjected to a NOT, then that criterion applies if it
is NOT met
The logic in the caching works like this: filters are OR
So if a request matches all the criteria of any of the filters then it will be cached. Otherwise it will not be cached.
A common trap is this. You want to say
This would achieve absolutely nothing. bob would not make it through on the Not User: Username equals bob rule. However his username is not Mary, so he would make it through on the
second rule.
Conversely mary would be denied on one, but make it through on the other, as
no-one can have two usernames.
What this really means is
To make this rule work, both these must hold:
a. Don
b. Don
So, the actual logic is: cache files that are NOT requested by bob, AND NOT
requested by mary. This would result in a single filter with 2 criteria as
demonstrated in the picture above.
Note:
Negative rules (i.e. caching depending on something not being met) become
complex. The previous example shows that an entry may be denied in one filter, but
allowed (either explicitly, or implicitly by not being denied) in another. If you want multiple filters, but disallow some specific criterion, make sure
you include this disallowed criterion in every filter.
This applies to all rules in WinGate (including caching rules, and access
rules).