> 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/help-center/cn/chan-pin-yu-gong-neng/oxylabs-shi-fou-zhi-chi-yong-yu-http3-lian-jie-de-masque.md).

# Oxylabs 是否支持用于 HTTP/3 连接的 MASQUE？

是。 [住宅代理](https://oxylabs.io/products/residential-proxy-pool) 原生支持 `UDP` 和 `HTTP/3` 通过 MASQUE 隧道（[RFC 9298 CONNECT-UDP](https://datatracker.ietf.org/doc/html/rfc9298)).

大多数代理路由会将流量强制通过一个 `TCP` 连接——通过 `HTTP CONNECT`，或 `SOCKS5` 没有 `UDP` 支持——这会导致 `HTTP/3` 请求降级为 `HTTP/2` 或 `HTTP/1.1`。到达 `HTTP/3` 以前，在不进行该降级的情况下访问目标是可行的，使用我们的 `SOCKS5` 带有……的端点 `UDP` 支持，但通常需要自定义客户端代码。&#x20;

MASQUE 维持端到端的 `QUIC` 通过我们的住宅出口节点建立连接，因此你的客户端会传输原生 `UDP` 流量直接发送到现代目标。连接建立所需的往返次数更少，没有单个丢失的数据包会拖慢其余部分，而且流量看起来就像普通的 `HTTP/3` 而不是可识别的代理隧道。

这是对我们现有 `HTTP`, `HTTPS`，以及 `SOCKS5` 协议的补充。有关详细的入口节点设置和协议规则，请访问 [协议](/products/proxies/residential-proxies/protocols.md) 页面，或查看 [MASQUE 集成指南](/products/proxies/residential-proxies/protocols.md#http-3).


---

# 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/help-center/cn/chan-pin-yu-gong-neng/oxylabs-shi-fou-zhi-chi-yong-yu-http3-lian-jie-de-masque.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.
