mhxandClaude Opus 4.8 8497f7de75 ✅ e2e mock: add AppSec scenario + custom remediation header assertion ...

Address review feedback on the binary e2e suite:

- mocklapi: add an AppSec WAF stand-in (--appsec-addr) that blocks any URI
  containing "rpc2" — the exact probe from examples/appsec-enabled — and allows
  the rest. Lets the suite exercise the plugin's AppSec wiring (header
  forwarding + allow/block enforcement) without the real CRS engine.
- new scenarios/appsec: benign request passes, /foo/rpc2 is 403.
- custom-ban-page: assert the banned response carries the custom remediation
  header (remediationHeadersCustomName), per review.
- README: drop the "don't open issues / AppSec intentionally absent" framing;
  describe what the suite actually covers, including AppSec wiring.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-06 21:33:52 +02:00

..

e2e/mock

✅ e2e mock: add AppSec scenario + custom remediation header assertion

2026-06-06 21:33:52 +02:00

.keytest

🍱 test validate

2022-12-04 16:58:06 +01:00