> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/products/cn/proxies/datacenter-proxies/response-codes.md).

# 响应代码

了解数据中心代理的不同响应代码，包括代码所指示的问题和常见状态错误。

这些是您在使用 Oxylabs 数据中心代理时可能遇到的最常见响应代码。

<table><thead><tr><th width="166">响应码</th><th width="268.3177083333333">错误消息</th><th>描述</th></tr></thead><tbody><tr><td><code>400</code></td><td><code>错误请求</code></td><td>无法理解该请求。请检查请求格式是否正确。</td></tr><tr><td><code>403</code></td><td><code>禁止访问</code></td><td>访问被拒绝：目标受限。如果您有任何问题，请联系支持团队或您的客户经理。</td></tr><tr><td><code>404</code></td><td><code>未找到</code></td><td>找不到指定的域名，或该资源不可用。</td></tr><tr><td><code>407</code></td><td><code>需要代理身份验证</code></td><td>未提供用户凭据 / 凭据不正确 / 用户正从未列入白名单的 IP 连接。</td></tr><tr><td><code>429</code></td><td><code>请求过多</code></td><td>用户已达到线程/并发会话限制。</td></tr><tr><td><code>500</code></td><td><code>内部服务器错误</code></td><td>我们的服务器出现了问题。请稍后再试。</td></tr><tr><td><code>502</code></td><td><code>错误网关</code></td><td>代理从上游服务器或目标服务器接收到无效响应。</td></tr><tr><td><code>503</code></td><td><code>服务不可用</code></td><td>连接目标服务器失败。解析目标服务器地址时发生 DNS 失败。</td></tr><tr><td><code>504</code></td><td><code>网关超时</code></td><td>代理服务器等待目标服务器响应时超时。通常大约需要 60 秒。</td></tr></tbody></table>


---

# 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://developers.oxylabs.io/products/cn/proxies/datacenter-proxies/response-codes.md?ask=<question>&goal=<user_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.