Audit a WAF 403 Dump Before a Model Sees the Cookie You Blocked
This story is from 2026-09-20. It is preserved in the archive; the latest stories are on the live feed.
Last Tuesday a platform engineer dropped a WAF 403 into our incident channel. Full request. Host, path, Cookie, Authorization, X-Real-IP. Then someone asked the question I now treat as a pager: can we just paste this into the model and ask why it got blocked? I read the dump twice. The model would…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-09-20 10:40 · DEV Community — AI
Audit a WAF 403 Dump Before a Model Sees the Cookie You Blocked