HTTP/3 (QUIC) Proxies
What are HTTP/3 and QUIC
HTTP/3 is the third major version of the HTTP protocol, standardized in 2022 (RFC 9114). The key difference from HTTP/2 is the use of the QUIC transport protocol instead of TCP.
QUIC (Quick UDP Internet Connections) is a transport protocol developed by Google, operating over UDP. It combines the functionality of TCP and TLS into a single layer, providing faster connection establishment and eliminating the head-of-line blocking problem.
Advantages of HTTP/3 for Proxies
1. Elimination of Head-of-Line Blocking
In HTTP/2, the loss of a single TCP packet blocks all streams within a connection. In HTTP/3, each stream is independent — the loss of a packet in one stream does not affect others.
For proxies, this means: if one request encounters packet loss, other requests through the same proxy continue to operate without delays.
2. Faster Connection Establishment (0-RTT)
HTTP/3 can establish a connection in 0 round-trips when reconnecting to a known server. For proxies that repeatedly access the same servers, this significantly reduces latency.
Comparison:
- TCP + TLS 1.3: 2-3 RTT for a new connection
- QUIC: 1 RTT for a new, 0 RTT for a resumed connection
3. Connection Migration
QUIC uses a Connection ID instead of binding to IP:port. The connection persists even when the IP address or network interface changes.
For mobile proxies, this is revolutionary: the connection is not broken when switching between Wi-Fi and 4G.
4. Built-in Encryption
QUIC encrypts not only data but also most of the protocol metadata. This complicates DPI (Deep Packet Inspection) and traffic analysis by intermediaries.
How HTTP/3 Works Through Proxies
Direct QUIC Proxying
The proxy forwards QUIC traffic (UDP) directly. This requires UDP proxying support, which most classic HTTP proxies do not provide.
CONNECT-UDP (RFC 9298)
A new method for tunneling UDP over HTTP proxies. It allows QUIC connections to pass through HTTP proxies without native QUIC support.
HTTP/3 Frontend, HTTP/2 Backend
The proxy accepts HTTP/3 from clients but connects to servers using HTTP/2 or HTTP/1.1. This is the most common scenario today.
Full HTTP/3
The proxy supports HTTP/3 in both directions. This is still rare but actively developing.
Current HTTP/3 Support in Proxies
| Proxy | HTTP/3 Frontend | HTTP/3 Backend | Status |
|---|---|---|---|
| Caddy | Yes | Experimental | Mature support |
| Nginx | Yes (1.25+) | No | Frontend only |
| HAProxy | In development | In development | Planned |
| Envoy | Yes | Yes | Active development |
| Traefik | Yes (3.0+) | Experimental | Basic support |
| Cloudflare | Yes | Yes | Full support |
HTTP/3 and Circumventing Blocks
Advantages for Circumvention
- UDP Traffic — many DPI systems are tailored for TCP; UDP filtering is less developed.
- Metadata Encryption — makes it harder to determine traffic content.
- Masquerading as QUIC — many legitimate services (Google, YouTube) use QUIC.
- Connection Migration — the connection persists when the IP changes.
Limitations
- UDP Blocking — some networks block all UDP except DNS.
- QUIC Fingerprinting — client can be identified by QUIC parameters.
- SNI — in the initial QUIC handshake, SNI is transmitted in the clear (ECH solves this).
QUIC Fingerprinting
Similar to HTTP/2 fingerprinting, anti-bot systems are beginning to analyze QUIC parameters:
- Transport Parameters — initial connection parameters
- Initial DCID Length — length of the initial Connection ID
- Preferred Address — migration support
- Token — 0-RTT behavior
A proxy must correctly mimic the QUIC fingerprint of the target browser.
Practical Recommendations
For Proxy Developers
- Add UDP support alongside TCP.
- Implement CONNECT-UDP for compatibility with HTTP/3 clients.
- Use libraries like quiche (Cloudflare), Quinn (Rust), ngtcp2 for QUIC implementation.
For Proxy Users
- Check if your provider supports HTTP/3.
- For DPI circumvention, QUIC proxies can be more effective than TCP-based solutions.
- Note that not all target websites support HTTP/3.
The Future of HTTP/3 Proxies
HTTP/3 is inevitably becoming the dominant protocol. Already, over 30% of web traffic uses HTTP/3. Key trends include:
- All major proxies will add full HTTP/3 support by 2025-2026.
- MASQUE (RFC 9484) will standardize proxying over HTTP/3.
- Connection migration will make mobile proxies more stable.
- Metadata encryption (ECH + QUIC) will enhance privacy.
Conclusion
HTTP/3 proxies represent the next evolutionary step in proxy technology. The QUIC protocol solves fundamental TCP problems (head-of-line blocking, slow handshake) and opens up new possibilities for mobile proxies and circumventing blocks. The transition to HTTP/3 is already underway, and the proxy industry is actively adapting.