Open nigoroll opened 8 months ago
That's a problem created by the nature of bits parameters. Are they additive by default? They support "none" and otherwise "all".
But is that not just the way we print the value? If yes, why would it impact the availability of "none" and "all" for param.set
?
bugwash @Dridi said he might want to send a PR
Expected Behavior
Using
none
andall
should work consistently, or a good reason why not should be apparent.Current Behavior
Using
none
works forfeature
, but not forvsl_mask
. Conversely,all
works forvsl_mask
, but not forfeature
.(cli)
Possible Solution
No response
Steps to Reproduce (for bugs)
No response
Context
Noticed while reviewing release docs
Varnish Cache version
No response
Operating system
No response
Source of binary packages used (if any)
No response