@@ -87,14 +87,23 @@ the regular expression is required by the Varnish cli interface.
87
87
88
88
Bans are checked when we hit an object in the cache, but before we
89
89
deliver it. *An object is only checked against newer bans *.
90
- The parameter `ban_any_variant ` is used to limit the number of possibly non
91
- matching variants that are checked against the ban list during lookup for a
92
- particular request. This means that at most `ban_any_variant ` variants will be
93
- evaluated, and possibly evicted, before looking for matching variants. A value
94
- of 0 means that every request would only evaluate bans against matching
95
- variants. In contrast, a value that is too high may cause a request to evaluate
96
- all variants against all active bans, which can add significant delays for
97
- configurations having a large number of variants and/or bans.
90
+
91
+ During lookup, object variants that may not satisfy the current request
92
+ are also tested against the ban list, which means that a ban may also
93
+ hit a non matching variant.
94
+
95
+ However, the parameter `ban_any_variant ` can be used to limit the number
96
+ of possibly non matching variants that are checked against the ban list during
97
+ lookup for a particular request. This means that at most `ban_any_variant `
98
+ variants will be evaluated, and possibly evicted, before looking for matching
99
+ variants. A value of 0 means that every request would only evaluate bans
100
+ against matching variants. In contrast, a value that is too high may cause a
101
+ request to evaluate all variants against all active bans, which can add
102
+ significant delays for configurations having a large number of variants
103
+ and/or bans.
104
+
105
+ In the next major release of varnish (8.0), the default value of
106
+ `ban_any_variant ` will be set to 0.
98
107
99
108
Bans that only match against `obj.* ` are also processed by a background
100
109
worker threads called the `ban lurker `. The `ban lurker ` will walk the
0 commit comments