Technology1 min read

How to Intercept HTTP/3 Traffic: QUIC and Qpack

By · Published by Everything Blog

In short

Capturing modern web requests requires proxies to terminate UDP-based QUIC sessions and handle QPACK compression across separate streams. Although observers can compute initial keys to view handshake packets, the remaining data is locked under TLS 1.3 encryption, making man-in-the-middle termination essential. Conventional proxying mechanisms also break down because tools lack broad support for the CONNECT-UDP method. Furthermore, applications such as Chromium restrict SOCKS5 routing to TCP, preventing QUIC streams from reaching traditional interceptors.

Key points

  • The transition from TCP to UDP in modern protocols prevents standard HTTP interceptors fr…: The transition from TCP to UDP in modern protocols prevents standard HTTP interceptors from functioning without dedicated QUIC support.
  • The CONNECT-UDP tunneling method remains insufficiently supported by modern proxy tools a…: The CONNECT-UDP tunneling method remains insufficiently supported by modern proxy tools and client applications.
  • Chromium limits its SOCKS5 implementation to TCP, blocking UDP-based QUIC traffic from re…: Chromium limits its SOCKS5 implementation to TCP, blocking UDP-based QUIC traffic from reaching proxies configured through standard methods.

Sources checked by our analysis pipeline: 1

A hands-on look at intercepting HTTP/3. How QUIC streams and QPACK work, what a proxy really sees, how to read and edit a request, and why the QPACK dynamic table makes some requests hard to read.

InterceptSuite Team

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. After that, the work is about streams and header compression: the request is not text any more, it is bytes on a QUIC stream, compressed with QPACK.

In this post we intercept real HTTP/3 traffic from curl and from Microsoft Edge. Then we use a small lab server to look at every byte, so the QUIC and QPACK parts are easy to follow.

Table of contents

- What changes with HTTP/3

- Why your usual proxy setup does not work

- Real…

Technology