HTTP Request Smuggling is not just a WAF bypass trick.
Most people miss the real issue:
The vulnerability comes from differences in how HTTP requests are parsed between:
* reverse proxy (frontend)
* backend server
CL.TE / TE.CL are only the basic cases. The deeper issues are more subtle:
* HTTP/2 to HTTP/1.1 translation ambiguity
* parsing inconsistencies across proxy chains
* cache poisoning via request desynchronization
* session hijacking without traditional auth or RCE bugs
Core idea:
One request can be interpreted as two different requests depending on which layer processes it.
The exploit happens in that mismatch.
It is not an application bug in the usual sense.
It is a systemic parsing disagreement across the HTTP stack.