Commit Graph
4 Commits
Author SHA1 Message Date
BaaRai 7c3d50d533 docs: describe applying the rewrite rules in the proxy
The status line said the proxy does not apply rules yet. Replace it with
the request and response phases, what exchange_rewrites records and how
the hashes are formed (plain SHA-256, keyed HMAC for sensitive actions),
the SSE and WebSocket behaviour, the 5 MiB response pass-through, the
snapshot limits (live slots are never deleted by the TTL), and the fact
that replays go through the proxy and are rewritten like captures.
2026-11-17 22:23:12 +01:00
BaaRai 8474131ba2 fix(server): match a kept sensitive value on type, header name and regex
A sensitive action sent without its value took the stored value at the same
position, so two sensitive actions of the same type and header name swapped
their values when reordered. The stored action is now found by type,
canonical header name and regex, wherever it stands, and exactly one must
match: none or several is refused (400, send the value).

The CRUD test no longer expects a refusal for a reordered action.
2026-11-17 00:12:09 +01:00
BaaRai 97f081ed63 fix(server): refuse a host change while a stored sensitive value is kept
An update that keeps the stored value of a sensitive action can no longer
change the rule's host matcher (compared case-insensitively): the value
would otherwise be written to a new destination. Same invariant as the
custom HTTP tools. The url_regex matcher is not compared, an accepted and
documented limit.
2026-11-17 00:12:09 +01:00
BaaRai 38d66d83b2 docs: describe the capture-proxy rewrite rules
Rule model, validation, limits, sensitive actions, API and storage, with the
statement that the proxy does not apply the rules yet. The README lists the
rules among the secrets encrypted at rest.

docs/ is ignored by .gitignore; the new file is force-added like the three
documents already tracked there.
2026-11-17 00:12:09 +01:00