smallwebwaf

149 Commits 16 Branches 2 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
sneak	1740ac6061	sww tests: wait for every starting line as long as the start takes (closes #331 ) check / check (push) Waiting to run Details Each test in internal/sww that waits for the starting line now waits until the line is written or sww exits, so a slow Core Rule Set compile on a loaded host no longer fails it. The two tests that run sww as a child process get its exit status from a goroutine that waits on it, and no longer kill it after 30 seconds; the waits after SIGTERM still end after waitLimit. A cleanup still kills each child process as its test ends and waits for it to exit. startRProxyProcess returns a stop function in place of the process and its output. Model: opus-5-5	2026-11-11 07:38:06 +00:00
clawbot	9bcbe5a3c8	Every time in UTC, and every day as YYYY-MM-DD (closes #313 ) check / check (push) In progress Details Every time the program stores, logs or compares is in UTC, whatever TZ says, and AbuseIPDB's day in `reputation.json` is a `YYYY-MM-DD` date. Times read from a state file are converted to UTC as they are read, so a file is written back with `Z` times only. A test runs `sww waf` with `TZ=Pacific/Kiritimati` and checks the process line, the request line and `clients.json`. `SPEC.md` states the rule and `AGENTS.md` makes it an iron rule. - The rate limit's `day` and `day_bytes` buckets keep a start time: each is a 24-hour bucket begun at an instant, not a calendar day. - New dependency `cloud.google.com/go`, of which only `civil` is built. - No migration: a `reputation.json` holding the old day form fails to load, naming the file. Model: opus-5-5	2026-11-11 06:00:53 +01:00
clawbot	f7e3190654	Rename discriminator to waf everywhere (closes #312 ) check / check (push) Successful in 5m58s Details The command is now `sww waf`, and the package is `internal/waf`. Types, functions, files, tests, comments, docs, the Dockerfile, the runit script, `script/`, compose examples, the log field `waf_line` and the `X-From-Waf` test header follow. No behaviour changes, and no setting changes name: rproxy already finds the waf through `SWRP_WAF_BACKEND`. Done with one `sed -i` (Discriminator and DISCRIMINATOR to WAF, discriminator to waf) over the files `git grep -i discriminator` listed, as sneak allowed for this rename, then `git mv` for the package and files. By hand afterwards: the header's spelling, which the linter requires, and the padding after `waf` in `sww`'s usage text. Model: opus-5-5	2026-11-11 02:43:16 +01:00

Author

SHA1

Message

Date

sneak

1740ac6061

sww tests: wait for every starting line as long as the start takes (closes #331 )

check / check (push) Waiting to run

Details

Each test in internal/sww that waits for the starting line now waits until
the line is written or sww exits, so a slow Core Rule Set compile on a
loaded host no longer fails it. The two tests that run sww as a child
process get its exit status from a goroutine that waits on it, and no
longer kill it after 30 seconds; the waits after SIGTERM still end after
waitLimit. A cleanup still kills each child process as its test ends and
waits for it to exit. startRProxyProcess returns a stop function in place
of the process and its output.

Model: opus-5-5

2026-11-11 07:38:06 +00:00

clawbot

9bcbe5a3c8

Every time in UTC, and every day as YYYY-MM-DD (closes #313 )

check / check (push) In progress

Details

Every time the program stores, logs or compares is in UTC, whatever TZ says, and AbuseIPDB's day in `reputation.json` is a `YYYY-MM-DD` date. Times read from a state file are converted to UTC as they are read, so a file is written back with `Z` times only. A test runs `sww waf` with `TZ=Pacific/Kiritimati` and checks the process line, the request line and `clients.json`. `SPEC.md` states the rule and `AGENTS.md` makes it an iron rule.

- The rate limit's `day` and `day_bytes` buckets keep a start time: each is a 24-hour bucket begun at an instant, not a calendar day.
- New dependency `cloud.google.com/go`, of which only `civil` is built.
- No migration: a `reputation.json` holding the old day form fails to load, naming the file.

Model: opus-5-5

2026-11-11 06:00:53 +01:00

clawbot

f7e3190654

Rename discriminator to waf everywhere (closes #312 )

check / check (push) Successful in 5m58s

Details

The command is now `sww waf`, and the package is `internal/waf`. Types,
functions, files, tests, comments, docs, the Dockerfile, the runit
script, `script/`, compose examples, the log field `waf_line` and the
`X-From-Waf` test header follow. No behaviour changes, and no setting
changes name: rproxy already finds the waf through `SWRP_WAF_BACKEND`.

Done with one `sed -i` (Discriminator and DISCRIMINATOR to WAF,
discriminator to waf) over the files `git grep -i discriminator`
listed, as sneak allowed for this rename, then `git mv` for the
package and files. By hand afterwards: the header's spelling, which
the linter requires, and the padding after `waf` in `sww`'s usage
text.

Model: opus-5-5

2026-11-11 02:43:16 +01:00