> 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/web-unblocker/response-codes.md).

# 响应代码

了解从 200 到 550 的最常见网页解锁器响应代码。了解每个 HTTP 状态的含义以及如何排查错误。

<table><thead><tr><th width="129.59895833333331">代码</th><th>状态</th><th>描述</th></tr></thead><tbody><tr><td><code>200</code></td><td><code>正常</code></td><td>一切正常，请求成功。</td></tr><tr><td><code>400</code></td><td><code>多个错误消息</code></td><td>请求结构错误。可能是参数拼写错误或值无效。响应正文会包含更具体的错误信息。</td></tr><tr><td><code>401</code></td><td><p><code>未提供授权头</code> <code>无效的授权头</code></p><p><code>未找到客户端</code></p></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>408</code></td><td><code>超时</code></td><td>请求超时。</td></tr><tr><td><code>429</code></td><td><code>请求过多</code></td><td>您已超过速率限制。</td></tr><tr><td><code>500</code>, <code>502</code>, <code>503</code></td><td><code>内部服务器错误</code></td><td>我们这边遇到了一些问题。请稍后再试。我们可能已经注意到这些问题，但你也可以随时联系我们并反馈。</td></tr><tr><td><code>550</code></td><td><code>重试次数过多后失败</code></td><td>出了点问题，我们未能完成您提交的任务。您可以免费重试，因为我们不会对失败的任务收费。如果仍然不行，请与我们联系。</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/web-unblocker/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.