OS, networking and concurrency · Question 34 of 50
What changed from HTTP/1.1 to HTTP/2 and HTTP/3?
Why the modern web got faster.
The answer
HTTP/1.1 sends one request at a time per connection, so browsers open about six connections per host, and a slow response blocks the ones behind it. Headers are plain text and repeated on every request.
HTTP/2 sends many requests at once over one TCP connection, interleaved as binary frames, with compressed headers, so tricks like bundling everything and splitting across domains matter less. But one lost TCP packet still stalls every stream on the connection. HTTP/3 runs over QUIC, on UDP: each stream recovers its own losses, the handshake is faster with TLS 1.3 built in, and a connection survives a switch from Wi-Fi to mobile data.
The picture
HTTP/1.1 conn 1: [req A ── resp A][req B ── resp B] one at a time, ~6 connections HTTP/2 one conn: [A1][B1][C1][A2][B2]... interleaved on one TCP connection HTTP/3 QUIC over UDP: streams A, B, C recover losses on their own
Is HTTP/2 server push still used?
Show the answer
Mostly not: Chrome removed it, and preload hints and 103 Early Hints took its place.