request-smuggling

Detect and map HTTP request smuggling vulnerabilities across proxies and backends.

5|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Yliken/ai4 --skill request-smuggling-yliken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-smuggling
Source: https://github.com/Yliken/ai4/tree/main/skills/request-smuggling
Command: npx skills add https://github.com/Yliken/ai4 --skill request-smuggling-yliken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HTTP request smuggling and desynchronization testing. Use when front proxies, CDNs, or load balancers disagree with the origin on message framing (Content-Length vs Transfer-Encoding), on HTTP/2→HTTP/1 translation, or when exploring client-side desync via browser fetch pipelines.

Core Features & Use Cases

  • Detect and map boundary disagreements across proxy hops, including front proxies, CDNs, and origin servers.
  • Validate CL.TE, TE.CL, TE.TE, HTTP/2 downgrade, and client-side desync scenarios with repeatable probes and evidence collection.
  • Use case: assess a network path to uncover where HTTP request framing differs between hops and verify mitigations.

Quick Start

Run authorized, controlled tests against a target to identify HTTP request smuggling boundaries and document the findings.

Frequently Asked Questions about request-smuggling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect HTTP request smuggling vulnerabilities across proxy hops?

HTTP request smuggling detection involves running repeatable probes across proxy hops to identify CL.TE, TE.CL, and TE.TE boundary desynchronization. It validates where front proxies and origin servers disagree on message framing and documents findings with logs.

What is the difference between CL.TE and TE.CL request smuggling?

CL.TE and TE.CL are HTTP request smuggling variants describing how proxies and backends disagree on message framing. CL.TE prioritizes Content-Length front and Transfer-Encoding back, while TE.CL reverses it. Repeatable probes validate both and collect evidence.

Can I test HTTP/2 downgrade smuggling and client-side desync?

Yes, testing HTTP/2 downgrade smuggling and client-side desync is supported. Probes validate HTTP/2 to HTTP/1 translation disagreements and browser fetch pipeline desynchronization, producing logs and evidence for analysis.

How do I validate HTTP request smuggling mitigations on my CDN?

Validate HTTP request smuggling mitigations by assessing network paths through your CDN to uncover where HTTP request framing differs between hops. Repeatable probes test CL.TE, TE.CL, and TE.TE variants to verify boundary disagreements are resolved.

What are the limitations of HTTP request smuggling probes?

HTTP request smuggling probes require authorized, controlled testing against targets. Limitations include the need for careful execution to avoid service disruption and the potential inability to cover all custom proxy configurations or non-standard HTTP implementations.