← All stories
● Covered by 1 source · 1 reportLow impact1 neutral

Intercepting HTTP/3 Traffic: Challenges with QUIC and QPACK

🔄 Updated 5d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • HTTP/3 uses QUIC over UDP, not TCP.
  • Traditional HTTP proxies cannot intercept HTTP/3.
  • Specialized proxies are needed for UDP/QUIC interception.
  • HTTP/3 requests are bytes on QUIC streams, compressed with QPACK.

HTTP/3's Departure from Traditional Proxies

HTTP/3 operates on QUIC, which in turn runs over UDP, a significant change from HTTP/1.1 and HTTP/2 that rely on TCP. This architectural shift means that standard HTTP proxies, such as Burp Suite, which are designed to handle HTTP over TCP, are unable to intercept HTTP/3 traffic. Their underlying structure does not support the UDP-based QUIC protocol.

Requirements for Intercepting HTTP/3

To intercept HTTP/3, a proxy must be able to relay UDP traffic and function as a man-in-the-middle for QUIC connections. Once the connection is intercepted, the challenge shifts to processing QUIC streams and QPACK header compression. Unlike previous HTTP versions where requests are often text-based, HTTP/3 requests are transmitted as bytes on a QUIC stream, compressed using QPACK.

Key Differences in HTTP/3 Protocol

HTTP/3 introduces three main changes compared to HTTP/1.1 or HTTP/2. Firstly, it runs on QUIC (RFC 9000) instead of TCP, with QUIC packets encapsulated within UDP datagrams, and TLS 1.3 integrated into the QUIC handshake. Secondly, clients learn about a server's HTTP/3 capability through ALPN (h3) or DNS HTTPS records, often starting with a TCP request before switching to QUIC. Lastly, HTTP/3 treats everything as a stream, with QUIC connections carrying multiple streams; client-initiated two-way streams handle requests and responses, while one-way streams manage housekeeping tasks.

Tooling for HTTP/3 Interception

Tools like InterceptSuite are designed for raw network traffic, including TCP, TLS, UDP, DTLS, and QUIC. Its ability to intercept UDP and QUIC makes it suitable for HTTP/3. However, the core tool does not include an HTTP parser for HTTP/3; it displays raw bytes. An official, open-source HTTP/3 extension for InterceptSuite decodes QUIC streams and QPACK headers into human-readable text, allowing for inspection and modification of the traffic.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

HTTP/3 traffic, which runs over QUIC and UDP, cannot be intercepted by traditional HTTP proxies built for HTTP over TCP. Intercepting HTTP/3 requires a proxy capable of relaying UDP and performing man-in-the-middle attacks on QUIC connections. The process involves handling QUIC streams and QPACK header compression, which differs from text-based HTTP/1.1 or HTTP/2 requests.