> 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/es/productos-y-funciones/oxylabs-admite-masque-para-conexiones-http-3.md).

# ¿Oxylabs admite MASQUE para conexiones HTTP/3?

Sí. [Residential Proxies](https://oxylabs.io/products/residential-proxy-pool) soporte nativo `UDP` y `HTTP/3` túnel a través de MASQUE ([RFC 9298 CONNECT-UDP](https://datatracker.ietf.org/doc/html/rfc9298)).

La mayoría de las rutas de proxy fuerzan el tráfico a través de una `TCP` conexión – mediante `HTTP CONNECT`, o `SOCKS5` sin `UDP` soporte – lo que hace que `HTTP/3` las solicitudes se degraden a `HTTP/2` o `HTTP/1.1`. Llegar a `HTTP/3` objetivos sin esa degradación ya era posible antes, usando nuestro `SOCKS5` endpoint con `UDP` soporte, pero a menudo requería código cliente personalizado. 

MASQUE mantiene una conexión de extremo a extremo `QUIC` a través de nuestros nodos de salida residenciales, por lo que tu cliente transmite tráfico nativo `UDP` directamente a objetivos modernos. La configuración de la conexión requiere menos viajes de ida y vuelta, ninguna sola pérdida de paquete retrasa el resto, y el tráfico se ve como ordinario `HTTP/3` en lugar de un túnel de proxy reconocible.

Es una adición a nuestros existentes `HTTP`, `HTTPS`, y `SOCKS5` protocolos. Para configuraciones detalladas de nodos de entrada y reglas de protocolo, visita la [Protocolos](/products/proxies/residential-proxies/protocols.md) página o explora la [Guía de integración de 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/es/productos-y-funciones/oxylabs-admite-masque-para-conexiones-http-3.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.