The SWW_WAF_ANOMALY_* descriptions said "Alert when ..." without saying what an alert does. Each threshold's row in the README settings table now says crossing it sends one alert to the alert destinations, and that no client is banned, rate limited or blocked. The two prefix settings and SWW_WAF_ANOMALY_WATCHED_NETS set no threshold, so they say instead that their thresholds only send alerts.
"Anomaly" is explained once in the README's configuration notes and once at the top of "Anomaly thresholds" in docs/settings.md. That section lists the setting names without per-setting descriptions. No code prints these descriptions, and no setting is renamed.
make fmt realigned the whole README settings table, so most of the README diff is whitespace.
Model: opus-5-5
Closes https://git.eeqj.de/sneak/smallwebwaf/issues/412
The `SWW_WAF_ANOMALY_*` descriptions said "Alert when ..." without saying what an alert does. Each threshold's row in the README settings table now says crossing it sends one alert to the alert destinations, and that no client is banned, rate limited or blocked. The two prefix settings and `SWW_WAF_ANOMALY_WATCHED_NETS` set no threshold, so they say instead that their thresholds only send alerts.
"Anomaly" is explained once in the README's configuration notes and once at the top of "Anomaly thresholds" in `docs/settings.md`. That section lists the setting names without per-setting descriptions. No code prints these descriptions, and no setting is renamed.
`make fmt` realigned the whole README settings table, so most of the README diff is whitespace.
Model: opus-5-5
Each SWW_WAF_ANOMALY_ threshold's description now says crossing it sends
one alert to the alert destinations and bans, rate limits and blocks no
client. The prefix and watched-netblock settings say their thresholds
only alert. README's configuration notes and docs/settings.md explain
"anomaly" once.
Model: opus-5-5
Each byte anomaly threshold's row said "when more than this many bytes,
as SWW_WAF_BYTES_COUNTED counts them, are counted for ...": the inserted
clause pushed the verb back, in sentences of up to 30 words. Each now
says "when more bytes than this are counted for ...", and names
SWW_WAF_BYTES_COUNTED in a sentence of its own, as the byte limits' rows
do.
Model: opus-5-5
Every SWW_WAF_ANOMALY_ threshold's description now says it only sends an alert and bans, rate limits and blocks no client, and "anomaly" is explained where the settings are introduced, as #412 asks.
Model: opus-5-5
Verdict: PASS
Head: 39f33873359839c71d3646b9872fcc3b1fe8d92d
Every `SWW_WAF_ANOMALY_` threshold's description now says it only sends an alert and bans, rate limits and blocks no client, and "anomaly" is explained where the settings are introduced, as https://git.eeqj.de/sneak/smallwebwaf/issues/412 asks.
Model: opus-5-5
Every anomaly setting now says its threshold only sends an alert and bans, rate limits and blocks no client, and "anomaly" is explained where the settings are introduced, as #412 asks.
Model: opus-5-5
Verdict: PASS
Head: 4fb4c12ffd8c59eeaadda9920d16febcd72a7999
Every anomaly setting now says its threshold only sends an alert and bans, rate limits and blocks no client, and "anomaly" is explained where the settings are introduced, as https://git.eeqj.de/sneak/smallwebwaf/issues/412 asks.
Model: opus-5-5
clawbot
merged commit 9f42460f70 into next2026-11-19 10:58:28 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #412
The
SWW_WAF_ANOMALY_*descriptions said "Alert when ..." without saying what an alert does. Each threshold's row in the README settings table now says crossing it sends one alert to the alert destinations, and that no client is banned, rate limited or blocked. The two prefix settings andSWW_WAF_ANOMALY_WATCHED_NETSset no threshold, so they say instead that their thresholds only send alerts."Anomaly" is explained once in the README's configuration notes and once at the top of "Anomaly thresholds" in
docs/settings.md. That section lists the setting names without per-setting descriptions. No code prints these descriptions, and no setting is renamed.make fmtrealigned the whole README settings table, so most of the README diff is whitespace.Model: opus-5-5
Verdict: PASS
Head:
39f3387335Every
SWW_WAF_ANOMALY_threshold's description now says it only sends an alert and bans, rate limits and blocks no client, and "anomaly" is explained where the settings are introduced, as #412 asks.Model: opus-5-5
Verdict: PASS
Head:
4fb4c12ffdEvery anomaly setting now says its threshold only sends an alert and bans, rate limits and blocks no client, and "anomaly" is explained where the settings are introduced, as #412 asks.
Model: opus-5-5