> For the complete documentation index, see [llms.txt](https://www.axisnow.io/zh/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.axisnow.io/zh/docs/edge/policies/access-control/faq.md).
# 常见问题
通用访问控制使用中的常见疑问与排错
配了跳过规则，请求为什么还是被后面的规则拦了？
不开选项的跳过只表示这条规则放行，后面的规则照常评估。白名单规则要开**绕过剩余规则**，想同时免于限速再开**绕过速率控制插件**。
怎么先观察一条规则会命中哪些请求？
先用不开任何选项的跳过规则承载同样的条件：请求照常处理，但计入命中并产生日志。在洞察页看命中数和命中来源符合预期后，再把动作改成阻断或挑战。
只放行办公网的规则把所有请求都拦了
通常是边缘前面有 CDN 或负载均衡，到达边缘的是代理地址，在日志检索里看任意一条请求的客户端 IP 即可确认；配置[真实客户端 IP](/zh/docs/edge/policies/real-ip.md)后再试。
误封了自己的 IP 怎么办？
没有手动解封，等封禁到期。期间先禁用或修正那条规则，避免到期后再次被封。
开启挑战后页面加载不完整、接口返回 403
挑战规则命中了页面引用的脚本、图片或接口请求：验证页只能在浏览器里作为页面完成，这些请求收到的是 403 Forbidden 的验证页。把条件限定在 HTML 页面，排除接口路径和静态文件后缀，写法见[防护场景 › 对可疑流量挑战](/zh/docs/edge/policies/access-control/use-cases.md#challenge)；API、移动端 SDK 和服务端调用无法通过挑战，它们的高频问题交给速率控制的阻断。
通过验证后又反复收到验证页
凭证与客户端 IP 绑定，移动网络或多出口的办公网换了 IP 要重新验证；凭证按域名下发，同一站点的每个域名各验证一次；浏览器禁用 Cookie 或关闭即清除时保存不了凭证；命中了另一条挑战规则，或凭证已过**通过有效期**。
第三方挑战的验证组件报错或验证不通过
先核对提供商设置里的密钥和控制台里的域名列表，见[工作原理 › 挑战](/zh/docs/edge/policies/access-control/how-it-works.md#challenge-details)。设置无误时是网络问题：访客的浏览器要能加载提供商的脚本，边缘节点要能访问提供商的校验接口。
搜索引擎需要单独放行吗？
IP 封禁不封已验证的 Bot，阻断和挑战会。有按地区或挑战的规则时，前面放一条「已验证的 Bot 等于 true」、开启**绕过剩余规则**的跳过规则，见[防护场景 › 可信来源跳过全部规则](/zh/docs/edge/policies/access-control/use-cases.md#trusted)。不按 User Agent 放行，它可以任意伪造。
日志里查不到某个被拦的请求
数据有约一分钟的延迟；日志经过采样；或者这个来源正处于封禁期，封禁期内不产生日志，去 IP 封禁记录里找。
---
# 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://www.axisnow.io/zh/docs/edge/policies/access-control/faq.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.