⚡

HTTP/2 Server Push & Stream Multiplexing

Simple

Free preview · 2 of 5 steps

HTTP/2: binary framing and multiplexed streams

HTTP/1.1 sends text over TCP — one request per connection (or 6 parallel connections). HTTP/2 replaces text with a binary framing layer: every request/response is broken into frames, each carrying a stream ID.

Multiple streams share one TCP connection. A slow stream doesn't block others (within HTTP — TCP-level head-of-line blocking still exists). This is the core improvement that makes HTTP/2 faster without multiple connections.

Packets in motion — click to inspect:

1 / 2

Space to play/pause · ← → to step