--- title: The Most Overlooked Vulnerability — Http request Smuggling description: HTTP Request Smuggling exploits ambiguity in how front-end and back-end servers parse HTTP/1.1 request boundaries using Content-Length and Transfer-Encoding... canonical: https://daily.dev/posts/the-most-overlooked-vulnerability-http-request-smuggling-bkxsg4njj twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The Most Overlooked Vulnerability — Http request Smuggling | daily.dev og:description: HTTP Request Smuggling exploits ambiguity in how front-end and back-end servers parse HTTP/1.1 request boundaries using Content-Length and Transfer-Encoding... og:url: https://daily.dev/posts/the-most-overlooked-vulnerability-http-request-smuggling-bkxsg4njj og:image: https://api.daily.dev/og/posts/bKxSG4NJj.png og:image:alt: The Most Overlooked Vulnerability — Http request Smuggling og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The Most Overlooked Vulnerability — Http request Smuggling **[InfoSec Write-ups](https://daily.dev/sources/infosecwriteups)** · 5 min read · 0 upvotes · 0 comments ## Summary HTTP Request Smuggling exploits ambiguity in how front-end and back-end servers parse HTTP/1.1 request boundaries using Content-Length and Transfer-Encoding headers. When these servers rely on different headers to determine where a request ends, an attacker can inject a smuggled request into the connection pipeline. The three main variants are CL.TE, TE.CL, and TE.TE. Real-world impacts include WAF bypass, session hijacking, cache poisoning, and access to internal endpoints. Mitigations include rejecting requests with both headers, normalizing ambiguous requests at the front-end, and migrating to HTTP/2, which uses binary frames with explicit lengths and eliminates this ambiguity entirely. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the difference between CL.TE and TE.CL HTTP request smuggling attacks? CL.TE occurs when the front-end server trusts the Content-Length header while the back-end trusts Transfer-Encoding, causing the back-end to terminate the request early and treat leftover bytes as a new request. TE.CL is the reverse: the front-end trusts Transfer-Encoding while the back-end trusts Content-Length, causing a similar desync but with the mismatch flipped between the two servers. _Teams hardening proxy and app-server pairs against desync bugs can track write-ups like this on daily.dev._ ### How does HTTP/2 eliminate request smuggling vulnerabilities that affect HTTP/1.1? HTTP/2 does not rely on Content-Length or Transfer-Encoding headers to determine where a request ends. Instead it sends data in binary frames, each with its own explicit length, removing the ambiguity in HTTP/1.1 that allows front-end and back-end servers to disagree about request boundaries and enables smuggling attacks. _Developers weighing an HTTP/2 migration for security reasons can follow protocol deep dives on daily.dev._ ### How can a web application defend against HTTP request smuggling attacks? Reject any request that specifies both Content-Length and Transfer-Encoding headers, normalize or reject ambiguous requests at the front-end, keep front-end and back-end parsers consistent or use the same software stack, and use HTTP/2 end-to-end where possible since it removes the header ambiguity entirely. _Security-conscious engineers building proxy hardening checklists can find similar guidance on daily.dev._ ## Similar posts on daily.dev - [Post Mortem: HTTP Request Smuggling Vulnerability](https://daily.dev/posts/post-mortem-http-request-smuggling-vulnerability-36fsdzezd) · Crystal · 7 upvotes · 0 comments - [Understanding the worst .NET vulnerability ever: request smuggling and CVE-2025-55315](https://daily.dev/posts/understanding-the-worst-net-vulnerability-ever-request-smuggling-and-cve-2025-55315-qljqff7f0) · .NET Escapades · 8 upvotes · 0 comments - [When Proxies Become Attack Vectors Through Header Injection](https://daily.dev/posts/when-proxies-become-attack-vectors-through-header-injection-lvjjpqdyu) · Security Boulevard · 1 upvotes · 0 comments - [Fixing request smuggling vulnerabilities in Pingora OSS deployments](https://daily.dev/posts/fixing-request-smuggling-vulnerabilities-in-pingora-oss-deployments-q2opmcgab) · Cloudflare · 0 upvotes · 0 comments --- Tags: [#appsec](https://daily.dev/tags/appsec), [#web-security](https://daily.dev/tags/web-security) [View this post on daily.dev](https://daily.dev/posts/the-most-overlooked-vulnerability-http-request-smuggling-bkxsg4njj) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The Most Overlooked Vulnerability — Http request Smuggling","url":"https://daily.dev/posts/the-most-overlooked-vulnerability-http-request-smuggling-bkxsg4njj","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-most-overlooked-vulnerability-http-request-smuggling-bkxsg4njj"},"datePublished":"2026-08-05T07:18:39.773Z","dateModified":"2026-09-14T08:43:45.100Z","description":"HTTP Request Smuggling exploits ambiguity in how front-end and back-end servers parse HTTP/1.1 request boundaries using Content-Length and Transfer-Encoding...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6b1969c3052b26e3e401885b9cf7db90?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6b1969c3052b26e3e401885b9cf7db90?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfoSec Write-ups","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfoSec Write-ups","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/f0dc21b5bbfd46fda36f7b4b53dd1705","url":"https://daily.dev/sources/infosecwriteups"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-most-overlooked-vulnerability-http-request-smuggling-bkxsg4njj","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"appsec,web-security","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfoSec Write-ups","item":"https://daily.dev/sources/infosecwriteups"},{"@type":"ListItem","position":3,"name":"The Most Overlooked Vulnerability — Http request Smuggling"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-most-overlooked-vulnerability-http-request-smuggling-bkxsg4njj#faq","mainEntity":[{"@type":"Question","name":"What is the difference between CL.TE and TE.CL HTTP request smuggling attacks?","acceptedAnswer":{"@type":"Answer","text":"CL.TE occurs when the front-end server trusts the Content-Length header while the back-end trusts Transfer-Encoding, causing the back-end to terminate the request early and treat leftover bytes as a new request. TE.CL is the reverse: the front-end trusts Transfer-Encoding while the back-end trusts Content-Length, causing a similar desync but with the mismatch flipped between the two servers. Teams hardening proxy and app-server pairs against desync bugs can track write-ups like this on daily.dev."}},{"@type":"Question","name":"How does HTTP/2 eliminate request smuggling vulnerabilities that affect HTTP/1.1?","acceptedAnswer":{"@type":"Answer","text":"HTTP/2 does not rely on Content-Length or Transfer-Encoding headers to determine where a request ends. Instead it sends data in binary frames, each with its own explicit length, removing the ambiguity in HTTP/1.1 that allows front-end and back-end servers to disagree about request boundaries and enables smuggling attacks. Developers weighing an HTTP/2 migration for security reasons can follow protocol deep dives on daily.dev."}},{"@type":"Question","name":"How can a web application defend against HTTP request smuggling attacks?","acceptedAnswer":{"@type":"Answer","text":"Reject any request that specifies both Content-Length and Transfer-Encoding headers, normalize or reject ambiguous requests at the front-end, keep front-end and back-end parsers consistent or use the same software stack, and use HTTP/2 end-to-end where possible since it removes the header ambiguity entirely. Security-conscious engineers building proxy hardening checklists can find similar guidance on daily.dev."}}]} ```