HTTP/3 and QUIC Explained
HTTP/3 and QUIC Explained
We trace a web request from the application layer down to the transport: what HTTP/2 fixed, what it didn't, and how QUIC solves the remaining problems at the protocol level.
Topics covered:
- HTTP/1.1's head-of-line blocking and the 6-connection workaround
- HTTP/2 multiplexing: how streams solve HTTP-level blocking
- TCP head-of-line blocking: why one lost packet stalls all streams
- QUIC: UDP-based transport with per-stream ordering
- Connection migration: why mobile networks don't break QUIC connections
- 0-RTT resumption: sending data before the handshake completes
- TLS 1.3 integration: encryption is mandatory, not optional
- Adoption reality: CDN support, server support, and when to enable HTTP/3
Related articles
How HTTP/2 and HTTP/3 Change Everything
Multiplexing, server push, and QUIC — why keep-alive is the old answer and what the new protocols actually fix.
What Happens When You Call an API?
One request, traced end to end: DNS, TCP, TLS, HTTP, load balancing, server logic, and the database — with the real cost of every hop.
How TLS Actually Secures a Connection
From the ClientHello to the session ticket: what every message in a TLS handshake does, why certificates are the center of the trust model, and how TLS 1.3 changed the game.
More in Networking
Depth, delivered weekly
One technical dispatch a week — articles and episode notes before they go public.
One technical dispatch per week. No noise.