competition-request-normalization-smuggling

1# Competition Request Normalization Smuggling
2 
3Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.
4 
5Use this skill when request interpretation changes between proxy, middleware, and backend parser layers.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Map every parsing hop: client-facing proxy, gateway, app server, and downstream service.
122. Record path normalization, header canonicalization, transfer framing, and host derivation at each hop.
133. Capture one accepted baseline request and one differential request with minimal delta.
144. Prove which hop interprets the request differently.
155. Reproduce one minimal differential path that yields decisive behavior.
16 
17## Workflow
18 
19### 1. Map Parse And Routing Boundaries
20 
21- Record `Host`, forwarded headers, path decoding, slash collapsing, dot-segment handling, and case behavior.
22- Note `Content-Length`, `Transfer-Encoding`, chunk framing, and connection reuse behavior when relevant.
23- Keep edge parser and backend parser decisions side by side.
24 
25### 2. Prove Differential Interpretation
26 
27- Build paired requests that differ in one canonicalization dimension only.
28- Capture proxy logs, backend logs, route match, and downstream request shape.
29…