docs: bound the AbuseIPDB bans by the clients listed over the ban days
check / check (push) Failing after 1m36s
check / check (push) Failing after 1m36s
SPEC.md and the README said the bans for AbuseIPDB's blacklist are bounded by the blacklist. Each listed client stays banned for SWW_WAF_ABUSEIPDB_BAN_DAYS, so the bans held are those of every client listed over that time, which can be many more than one blacklist holds. Model: opus-5-5
This commit is contained in:
1 parent
b10986eae1
commit
3a9c67fa7b
2 files changed
+5
-3
No files matched your search
@@ -632,7 +632,8 @@ status for a size or time limit, such as `413` for a body too large.
|
||||
- Each limit is counted over a sliding window with a few integers per client.
|
||||
The table of clients and the bans for limits and attacks each have a bound
|
||||
(`SWW_WAF_MAX_TRACKED_CLIENTS`, `SWW_WAF_MAX_BANS`). The bans for AbuseIPDB's
|
||||
blacklist are bounded by the blacklist. So memory is bounded too.
|
||||
blacklist are bounded by the clients it listed over the last
|
||||
`SWW_WAF_ABUSEIPDB_BAN_DAYS` days. So memory is bounded too.
|
||||
- A ban refuses every request from its netblock until it ends. Requests refused
|
||||
under a ban count toward no limit. A permanent ban ends only when an admin
|
||||
lifts it.
|
||||
|
||||
Reference in new issue
Block a user