http-smuggling

To detect HTTP request smuggling vulnerabilities, this Skill analyzes inconsistent request parsing between frontend proxies and backend servers, specifically targeting CL.TE, TE.CL, and TE.TE parsing discrepancies using timing and differential response analysis.

Testing for CL.TE and TE.CL desync issues is achieved by applying HTTP protocol analysis and connection reuse testing to identify parsing inconsistencies, validating whether the infrastructure contains exploitable request manipulation scenarios.

Yes, you can evaluate WAF bypass and cache poisoning attack chains. The Skill analyzes potential impacts of HTTP desynchronization, validating request manipulation scenarios across multiple proxy layers within an authorized target.

Yes, HTTP request smuggling detection requires differential response evaluation. The workflow uses this alongside timing analysis and HTTP protocol analysis to identify parsing flaws and safely validate exploitable desynchronization issues.

To generate a safe validation report after identifying request parsing flaws, the Skill applies authorized web security assessment workflows, documenting CL.TE, TE.CL, and TE.TE testing results and confirming exploitable desynchronization issues safely.

You should not use HTTP request smuggling testing on unauthorized targets. The Skill requires an authorized web security assessment context, strictly applying safe vulnerability reporting workflows to legally validated infrastructure.