Skip to content
NewA calmer, faster ZeroHour
Toolsinfo

InterceptSuite post shows how to proxy HTTP/3 over QUIC

Original title: How to Intercept HTTP/3 Traffic: QUIC and Qpack

Hacker News · securityby anof-cyber ()16 min read2
AI summary · x-ai/grok-4.7Summaries by Vani AI

Usual TCP HTTP proxies miss HTTP/3 because QUIC uses UDP; the post redirects curl and Edge and decodes QPACK with an extension.

A blog post explains that HTTP/3 rides QUIC over UDP, so proxies built for HTTP over TCP never see it. InterceptSuite can relay UDP and sit in the middle of QUIC, while an open-source extension turns raw streams and QPACK headers into text. The walkthrough redirects curl 8.23.0 and Microsoft Edge without changing those apps' proxy settings, and notes that Chrome's SOCKS5 support does not relay UDP.

Key facts
  • The Windows curl build 8.21.0 lacks HTTP/3; winget build 8.23.0 lists it.
  • Initial QUIC packets use keys anyone can derive from the connection ID.
  • HTTP/3 CONNECT still tunnels TCP; CONNECT-UDP is a separate method.
  • The tool core shows raw bytes, not parsed HTTP.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

16 min read at interceptsuite.com

Short answer: HTTP/3 does not go through an HTTP proxy, because it runs over QUIC, and QUIC runs over UDP. Most HTTP proxies, such as Burp Suite, are built on HTTP over TCP, so they never see it. To intercept HTTP/3 you need a proxy that can relay UDP and can act as a man in the middle for QUIC.

Hacker News · security

By anof-cyber · interceptsuite.com

Read the full article at Hacker News · security

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.