HTTP/1.1 Must Die: What This Means for AppSec Leadership
portswigger.net | blog | #appsec | #request-smuggling | #http1-must-die | #burp-suite-dast | #enterprise-security | #http2
Summary
What AppSec leaders should take from HTTP/1.1 Must Die: desync attacks remain a systemic protocol-level threat, and auditing with Burp Suite DAST plus moving to upstream HTTP/2 is the fix.
- Published
- Collected
--- id: 241 title: "HTTP/1.1 Must Die: What This Means for AppSec Leadership" source_domain: portswigger.net source_url: "https://portswigger.net/blog/http-1-1-must-die-what-this-means-for-appsec-leadership" published_at: "2025-08-06T22:23:49Z" tags: ["appsec", "request-smuggling", "http1-must-die", "burp-suite-dast", "enterprise-security", "http2"] phying_url: "https://phying.com/item/241" lang: en --- # HTTP/1.1 Must Die: What This Means for AppSec Leadership ## Summary What AppSec leaders should take from HTTP/1.1 Must Die: desync attacks remain a systemic protocol-level threat, and auditing with Burp Suite DAST plus moving to upstream HTTP/2 is the fix. ## Intelligence Metadata - **Sources:** portswigger.net - **Published:** 2025-08-06T22:23:49Z - **Original:** https://portswigger.net/blog/http-1-1-must-die-what-this-means-for-appsec-leadership - **Phying News:** https://phying.com/item/241