> For the complete documentation index, see [llms.txt](https://docs.proxyshard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proxyshard.com/cn/chan-pin/about-udp/why-blocking-webrtc-doesnt-help.md).

# 为什么禁用 WebRTC 不能避免被识别

市场上几乎所有反检测浏览器都会简单地阻止 <mark style="color:purple;">WebRTC</mark> 以防止泄露。但这也是一个危险信号。对于大多数普通用户来说，<mark style="color:purple;">WebRTC</mark> 可以工作，如果它被禁用，那看起来也很可疑。

{% hint style="danger" %}
**唯一正确的做法是不阻止**<mark style="color:purple;">**WebRTC**</mark>**，而是通过UDP代理正确代理它。为此，浏览器或软件以及代理本身都必须支持它。**
{% endhint %}


---

# 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://docs.proxyshard.com/cn/chan-pin/about-udp/why-blocking-webrtc-doesnt-help.md?ask=<question>&goal=<endgoal>
```

`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.