Protocols
Saved & recent

HTTP/2

Also called: HTTP 2, HTTP multiplexing, h2

HTTP/2 carries HTTP messages in binary frames and multiplexes several exchanges on one TCP connection. Stream identifiers keep the exchanges distinct, and compressed fields reduce repeated metadata. A server can interleave data from different responses instead of finishing one whole response before starting the next.

For example, frames for an image and stylesheet can alternate while both resources load. This removes HTTP/1.1’s response-order bottleneck, but TCP still delivers one ordered byte stream: a missing TCP segment can hold up bytes belonging to several HTTP/2 streams. Multiplexing therefore improves concurrency without eliminating every source of waiting.

Read first
HTTP, TCP
Related
HTTP/1.1, HTTP/3, gRPC, Head-of-line blocking
Further reading
IETF RFC 9113 — HTTP/2
image · stream 1 stylesheet · stream 3 1 3 multiplexed HTTP/2 frames stream 1 stream 3 stream 1 stream 3 stream 1 stream 3 missing TCP segment receiver separates frames stream 1 stream 3 shared stall from TCP loss
HTTP/2 frames from different streams share a TCP connection. Their interleaving avoids HTTP/1.1 response ordering, but a missing TCP segment can delay delivery of later bytes from either stream.

View in the full Protocols collection