HTTP Multiplexing — Live

Three protocols carry the same concurrent streams across the wire. HTTP/1.1 makes each request cross one at a time; HTTP/2 lets many streams share one boat (a single TCP connection); HTTP/3 gives each stream its own boat over QUIC. Pick a protocol, tune the load, then drop a packet and watch who is bound to wait.

HTTP/1.1: one connection, one request at a time. Streams cross serially — request-level head-of-line blocking.

Client → Server one TCP connection, serial

0 streams stalled now
0.0s elapsed
0 packets delivered

How many requests race at once. More streams make the shared-boat stall more dramatic.

Request size — bigger responses spend longer on the wire and more time exposed to loss.

Per-stream status