HTTP topic
HTTP history
HTTP evolved in response to real constraints in publishing, connection reuse, scale, latency, security, and deployment. This sequence explains why major protocol features appeared and how modern HTTP continues to change.
Recommended foundation
Start here
This entry establishes the shared model used by the references, diagnostics, and experiments below.
HTTP History
From a CERN information problem to HTTP/0.9
HTTP began as the smallest practical interface between a universal document address and a remote hypertext document.
HTTP history
HTTP History
5 reviewed entries
intermediate
HTTP/1.0: when the growing Web needed real messages
HTTP/1.0 documented the message features implementations had added as the Web expanded beyond retrieving HTML documents.
intermediate
HTTP/1.1: persistent connections and the architecture of scale
HTTP/1.1 made connection reuse, virtual hosting, precise framing, richer caching, and intermediaries work at Web scale.
advanced
HTTP/2: multiplexing the same Web semantics
HTTP/2 replaced ordered text exchanges with compressed, multiplexed streams while preserving HTTP methods, statuses, fields, and URLs.
advanced
QUIC and HTTP/3: changing the transport beneath HTTP
HTTP/3 maps HTTP semantics onto QUIC, a secure UDP-based transport designed for independent streams and protocol evolution.
intermediate
What HTTP's history teaches about protocol evolution
HTTP evolves by preserving useful semantics, revising failed machinery, registering extensions, and learning from deployed behavior.