hn.today

How to Intercept HTTP/3 Traffic: QUIC and Qpack

interceptsuite.com77 points10 comments
Screenshot of How to Intercept HTTP/3 Traffic: QUIC and Qpack

HTTP/3 runs over QUIC, which carries traffic in UDP datagrams, so conventional HTTP proxies built for TCP do not see it. Interception requires redirecting UDP traffic or using a client that supports SOCKS5 UDP, and a proxy that can terminate QUIC and TLS. Once intercepted, HTTP is carried as bytes on QUIC streams: request-response pairs use bidirectional streams, while control and QPACK information use separate unidirectional streams. A raw-traffic proxy therefore needs an HTTP/3 decoder to display and edit requests. QUIC’s initial packets expose some handshake information, but application traffic remains encrypted unless the proxy is one of the connection’s endpoints.

Demonstrations with curl and Edge show both the possibilities and complications. Forcing curl to use HTTP/3 lets an intercepted User-Agent header be changed, and the server confirms the edit. Curl disables QPACK’s dynamic table, so its headers are easy to read. Edge supports a 64 KB table and many blocked streams, allowing later requests to refer to previously transmitted header entries and making decoding dependent on connection history. Intercepting Edge also requires redirecting its traffic and launching a test profile with settings to disable ECH and DNS HTTPS-record discovery, force QUIC, and trust the proxy’s certificate. SOCKS5 can relay UDP, but Chromium generally does not use that route for QUIC. The practical challenge is thus not simply proxy configuration: reliable inspection depends on handling UDP, acting as a QUIC endpoint, and tracking QPACK state.

Read on interceptsuite.com10 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Web

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.