> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/fr/web/request-smuggling.md).
# Contrebande de requêtes HTTP
Contrebande de requêtes HTTP, CL.TE, TE.CL, désynchronisation HTTP/2, contournement du front-end, tunneling et empoisonnement du cache.
Notes sur le HTTP Request Smuggling pour les laboratoires de la PortSwigger Web Security Academy, axées sur les étapes de test pratiques, la validation dans Burp Suite, le comportement des charges utiles et le flux de travail d’exploitation.
## Flux de test
1. Identifiez la fonctionnalité vulnérable et la requête, le paramètre, l’en-tête, le cookie ou le point d’injection côté navigateur pertinent.
2. Reproduisez le comportement dans Burp Suite avec une charge utile minimale avant d’intensifier l’attaque.
3. Validez l’impact avec une preuve de concept claire, comme l’accès au compte, la divulgation de données, l’exécution de code, le SSRF ou un changement d’état.
4. Conservez inchangés les charges utiles, les URL, les jetons et les identifiants du laboratoire tout en documentant le chemin d’exploitation.
## Laboratoires
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/fr/web/request-smuggling.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.