docs: say SWW_WAF_MAX_BANS bounds only the bans for limits and attacks
check / check (push) Successful in 4m40s
check / check (push) Successful in 4m40s
The bans for AbuseIPDB's blacklist do not count toward SWW_WAF_MAX_BANS, but SPEC.md and the README still said it bounds the bans and so the memory, docs/settings.md still called it all of waf's own bans, and the size of bans.json in docs/state-files.md left out the 10,000 or more bans a free account's blacklist adds. Model: opus-5-5
This commit is contained in:
1 parent
3060788ca3
commit
b10986eae1
4 files changed
+16
-12
No files matched your search
+2
-2
@@ -42,8 +42,8 @@ chooses between the two (see "The image's command" below).
|
||||
client's group, from 32 to 128.
|
||||
- `SWW_WAF_MAX_TRACKED_CLIENTS` (default `20000`): the most clients kept, a
|
||||
whole number above zero.
|
||||
- `SWW_WAF_MAX_BANS` (default `5000`): how many of its own bans `waf` keeps, a
|
||||
whole number above zero.
|
||||
- `SWW_WAF_MAX_BANS` (default `5000`): the most bans `waf` keeps for broken
|
||||
limits and attacks, a whole number above zero.
|
||||
|
||||
## Tokens
|
||||
|
||||
|
||||
Reference in new issue
Block a user