Course contentsShow
← Web Development
Lesson 2127 of 2,98239. Network PerformanceFree lesson

HTTP/3 and QUIC Protocol

Explore how HTTP/3 runs over UDP with QUIC to eliminate TCP head-of-line blocking.

HTTP/3 and QUIC Protocol

What you'll learn: How HTTP/3 eliminates TCP head-of-line blocking by running over UDP with the QUIC protocol.


The Problem HTTP/3 Solves

You just learned that HTTP/2 suffers from TCP head-of-line blocking: when a single TCP packet is lost, all multiplexed streams on that connection must wait for retransmission, even streams that received their data successfully. This happens because TCP guarantees ordered delivery at the transport layer.

HTTP/3 takes a revolutionary approach: it abandons TCP entirely and runs over UDP using a new protocol called QUIC (Quick UDP Internet Connections).

Why UDP?

UDP doesn't guarantee order or reliability—it just fires packets and forgets them. This sounds worse, but it gives QUIC the freedom to implement its own reliability per-stream instead of per-connection.

Analogy: Imagine a train (TCP) where every car must stay in order—if one derails, the whole train stops. Now imagine individual cars (UDP packets) that can travel independently on separate tracks (QUIC streams). If one car has trouble, the others keep moving.

How QUIC Works

QUIC builds reliability, congestion control, and multiplexing into the protocol itself, but at the stream level rather than connection level. Each HTTP/3 stream is independent:

  • Lost packets only affect their specific stream
  • Other streams continue receiving and processing data
  • Zero-RTT connection establishment (faster than TCP+TLS)
  • Built-in encryption (TLS 1.3 is mandatory)

Real-World Benefits

  • Eliminates head-of-line blocking across streams
  • Faster connection establishment (one round trip instead of multiple)
  • Better mobile performance when switching networks (connection migration)

Key Takeaway: HTTP/3 uses QUIC over UDP to implement per-stream reliability, eliminating the TCP head-of-line blocking problem that plagued HTTP/2 while maintaining all its multiplexing benefits.