Files

T

check / check (push) Failing after 23m49s

Details

rproxy and servewaf replace the one-process smallwebwaf (closes #172 , closes #165 )

`smallwebwaf` with no command now prints the commands and exits with status 2.
The image runs rproxy, or servewaf with SMALLWEBWAF_COMMAND=servewaf. The
passing-on code, its settings and its log fields and metric go. internal/proxy
keeps the checks, answers, reports and own endpoints; its tests run through the
real rproxy. The documents describe the pair.

Judgement call: clients.json keeps token_refused, since state files refuse unknown fields.
Deviation: script/gitea-requests sets SWWAF_LOG_REQUEST_HEADERS, to label requests.

Model: opus-5-5

2026-11-05 10:33:24 +00:00

2.8 KiB

Raw Blame History

Admin endpoints

The endpoints under /_smallwebwaf/, what each takes and what each answers. smallwebwaf servewaf answers them at its own address, on the private network. "Admin endpoints" in SPEC.md says how their tokens work.

GET /_smallwebwaf/healthz: 200 and ok, to anyone.
GET /_smallwebwaf/metrics: the metrics, for SWWAF_METRICS_TOKEN (see metrics.md).
GET /_smallwebwaf/bans: every ban held, under bans, each as bans.json lists it. Needs SWWAF_ADMIN_TOKEN, as do the three below.
POST /_smallwebwaf/bans: bans a netblock. The body is a JSON object of netblock, duration and, if you like, reason. netblock is a netblock such as 203.0.113.0/24, or a client's address, which bans its IPv4 netblock (SWWAF_BAN_SCOPE_V4_PREFIX) or its IPv6 group. duration is a duration such as 1h or 7d, or permanent. A bad body is answered 400, saying what is wrong:
- one that is not such an object, or has another field;
- one longer than 4 KiB;
- one that names an IPv4-mapped netblock, or an address with a zone.
DELETE /_smallwebwaf/bans/<client>: lifts every active ban covering the address <client>. It answers 404 when none is active.
GET /_smallwebwaf/clients/<ip>: what servewaf knows of the client. Under client, its counters and history as clients.json holds them, or null when clients.json does not hold it. Under bans, every ban covering the address, with its notes.
POST /_smallwebwaf/report: takes rproxy's report, without a token. It answers 204, or 400 to a body that is no report (see "The report" in SPEC.md).

No check runs on these requests. A missing or wrong token is answered 401. An endpoint whose token is unset answers 404, as does any other path.

smallwebwaf rproxy answers only the health check of these, at its own address. It asks servewaf about any other request under /_smallwebwaf/. One that passes the checks is answered 404, so that the app never sees that prefix (see "rproxy" in SPEC.md).

Examples

With SWWAF_ADMIN_TOKEN set, the token in $TOKEN, and servewaf reached as servewaf:8080 on its network:

# Every ban.
curl -H "Authorization: Bearer $TOKEN" http://servewaf:8080/_smallwebwaf/bans

# Ban 203.0.113.0/24 for seven days.
curl -H "Authorization: Bearer $TOKEN" \
    --json '{"netblock": "203.0.113.0/24", "duration": "7d", "reason": "probes for logins"}' \
    http://servewaf:8080/_smallwebwaf/bans

# Lift the bans on 203.0.113.9.
curl -H "Authorization: Bearer $TOKEN" -X DELETE \
    http://servewaf:8080/_smallwebwaf/bans/203.0.113.9

# What servewaf knows of 203.0.113.9.
curl -H "Authorization: Bearer $TOKEN" \
    http://servewaf:8080/_smallwebwaf/clients/203.0.113.9

2.8 KiB Raw Blame History

Admin endpoints

Examples

2.8 KiB

Raw Blame History