competition-request-normalization-smuggling

This skill identifies parser drift and request-smuggling indicators by applying deterministic evidence collection. It captures baseline and differential requests across proxy-to-backend boundaries to trace where path normalization and header handling diverge.

Trace path normalization differences by mapping parse and routing boundaries across client proxy, gateway, app server, and downstream service. Capture differential request pairs to identify where parsing differs and how routing changes occur.

Collect reproducible evidence by enforcing deterministic collection within a controlled sandbox workflow. Preserve raw evidence and produce a replayable minimal differential path to document exactly where routing diverges for remediation.

Yes, you can diagnose header handling discrepancies by mapping parse boundaries between your gateway and app server. The skill traces differences in header interpretation to prevent hidden proxy and backend misinterpretations.

You need the sandbox orchestrator active to trace differential request paths. Once active, identify a differential path and document where routing diverges across your multi-hop architecture.

Yes, this approach works for CTF security challenges involving request smuggling. It applies differential request pairing and deterministic evidence collection to trace parser drift across proxy-to-backend boundaries.