request-smuggling

Test HTTP request smuggling by probing boundary desynchronization between front-end proxies and origin servers. Craft requests to detect CL.TE, TE.CL, and TE.TE variants, mapping potential impact on caching and authentication within controlled environments.

HTTP boundary desync occurs when front-end proxies and origin servers disagree on Content-Length and Transfer-Encoding framing, or during HTTP/2 downgrades. This misalignment allows request smuggling by shifting how boundaries are interpreted between network layers.

Detect CL.TE and TE.CL desync variants by sending crafted requests across a test path and observing how boundaries shift between the front-end and origin. This identifies misalignment in Content-Length and Transfer-Encoding processing across proxies.

HTTP request smuggling testing works with H2 downgrades, load balancers, and reverse proxies. It identifies boundary disagreements during HTTP/2 downgrades and applies safe fuzzing practices across various CDN configurations.

Safely testing HTTP request boundary desynchronization requires knowledge of HTTP/1.1 framing, HTTP/2 downgrades, and safe fuzzing practices. You need explicit authorization and guardrails to ensure controlled testing environments.

HTTP request smuggling causes queue poisoning and caching issues because boundary desynchronization allows injected requests to be interpreted differently by the origin. This maps smuggling pathways that disrupt authentication and cache state across proxies.