Don't Panic — HTTP/2 and HTTP/3

HTTP/2 and HTTP/3 are not two replacement HTTPs waiting outside the old HTTP's house with boxes. They keep the familiar meaning of methods, status codes, fields, and content. The useful change is how one connection carries those messages. HTTP/2 divides them into frames and interleaves streams over TCP. HTTP/3 carries HTTP over QUIC, which uses UDP underneath. Same conversation, different plumbing, and plumbing is where the queues live.

Before HTTP/2, concurrent browser work often meant several TCP connections, or pipelining with an unfortunate tendency for one request to hold up the procession. HTTP/2 gives each exchange a stream, so a large response does not have to occupy the entire HTTP message lane. But TCP still delivers one ordered run of bytes. Lose one segment and later bytes wait, which can leave several streams staring at the same missing parcel.

HTTP/3 changes that particular arrangement. QUIC orders data within each stream, not across every stream. If one stream loses data, another stream whose data arrived can continue. This is not a universal permission slip stamped “faster.” Congestion, flow control, server queues, application dependencies, and QPACK field compression can still make progress wait. The protocol moved a queue; it did not repeal queues, which was probably beyond its charter.

The surprising part is that protocol version is decided per hop. A browser can speak HTTP/3 to an edge proxy, while that proxy speaks HTTP/2 to an origin. An HTTPS address does not carry a version label. HTTP/2 is commonly chosen with ALPN during a TLS handshake. HTTP/3 needs a QUIC connection and can be advertised through Alt-Svc. That is why a rollout normally keeps the earlier path: some networks obstruct UDP, and a graceful fallback is compatibility rather than defeat.

The Intro explains the connection models, loss behavior, compression, discovery, 0-RTT replay risk, and migration in full. The Slides place the two stacks and their failure modes beside each other. Keep the Cheatsheet nearby when a frame, stream, flow-control window, or deployment signal needs a precise name. The quiz then asks whether the mental model survived contact with the wire.

Don't Panic — HTTP/2 and HTTP/3

Relevant careers