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
+3
-1
@@ -157,7 +157,9 @@ A cache file. routewatch's answers from the last hour, one per line:
|
||||
- `bans.json`: about 1.2 KiB per ban, at most about 2.5 KiB, so about 6 MiB at
|
||||
the default `SWW_WAF_MAX_BANS`. Written every 15 minutes, a full file comes to
|
||||
about 600 MiB of writes a day, and a hundred new bans a day add about 600 MiB
|
||||
more.
|
||||
more. A ban for AbuseIPDB's blacklist takes about 1 KiB. A free account's
|
||||
blacklist lists 10,000 clients, so it adds at least 10 MiB, and 1 GiB of
|
||||
writes a day.
|
||||
- `lookups.json`: about 150 bytes per answer, under 1.5 GiB of writes a day when
|
||||
full.
|
||||
- `routewatch.json`: about 120 bytes per answer, at most about 12 MiB.
|
||||
|
||||
Reference in new issue
Block a user