Computer Networks • Week 4–5
01 / 13HTTP/1.1 vs 2 vs 3: multiplexing, streams, QUIC
HTTP semantics evolve more slowly than HTTP transport behavior. HTTP/1.1 uses textual messages and traditionally relies on one request/response stream per TCP connection at a time unless multiple connections are used. HTTP/2 introduces binary framing, multiplexed streams, HPACK header compression and prioritization features. HTTP/3 maps HTTP semantics onto QUIC streams.
StackShade deck
Predict → explain → retrieve