May 14, 2015

HTTP/2 standardized

RFC 7540 published HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages./2 on May 14, 2015 — multiplexed requests, header compression, and server push over a single TCPTransmission Control Protocol — a reliable, connection-oriented protocol used on the internet. connection.

What it was for

HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages./2 evolved from Google's SPDY protocol — browsers and CDNs adopted it to cut page load latency. Multiple requests share one connection without head-of-line blocking at the HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. layer; HPACK compresses headers. gRPC and many APIs run over HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages./2 today. Example: a page loading dozens of assets in parallel on one TLSTransport Layer Security — encryption that protects data in transit on the web and networks. connection to the origin.

Companies

  • IETF

Why it's here

HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages./2 was the first major HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. revision since 1.1 and addressed real-world web performance bottlenecks.

Why it mattered

It made multiplexing and header compression standard, paving the way for HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages./3 over QUIC.

What it solved

HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages./1.1's one-request-per-connection model caused latency and inefficient use of modern networks.

Related