This document discusses HTTP desync attacks, also known as request smuggling. It begins with an overview of the topic and various techniques for desynchronizing requests between the frontend and backend servers, such as using conflicting header fields. It then provides case studies of how desync attacks have been used in the past to bypass security rules, extract sensitive responses, and poison caches. The document concludes with recommendations for defenses, such as normalizing requests and using HTTP/2.