How a Google experiment became the backbone of the modern web

How a Google experiment became the backbone of the modern web
Image: Intellect (generated)

In short: The internet's primary language underwent a massive overhaul to fix a fundamental bottleneck: head-of-line blocking. By borrowing architecture from a private research project, HTTP/2 enabled multiple requests to travel simultaneously over a single connection, drastically accelerating how your browser loads complex pages.

HTTP/2 was not built from scratch; it was derived from SPDY, an experimental protocol spearheaded by Google to reduce latency. In July 2012, Facebook provided feedback recommending that the new standard be based on SPDY. Consequently, the initial draft of HTTP/2, published in November 2012, was essentially a straight copy of the SPDY protocol. This transition was finalized when the IETF approved HTTP/2 as a Proposed Standard on February 17, 2015, with its first specification, RFC 7540, appearing in May of that year.

The core innovation lies in multiplexing. While HTTP/1.1 often required separate connections for different resources, HTTP/2 allows multiple requests and responses to be sent concurrently over a single TCP connection. It also introduced 'Server Push,' where a server can preemptively send data it knows a browser will need before the browser even asks for it. However, because it still relies on a single TCP pipe, it suffers from a design flaw: if a single TCP packet is lost or delayed, all other transactions on that connection are blocked. This specific issue is what the successor, HTTP/3, aims to solve.

The protocol's journey was marked by controversy. Critics, including Poul-Henning Kamp, argued the standard was rushed and overly complex, violating protocol layering principles by duplicating flow control. There was also significant debate over encryption. While the standard doesn't strictly require it, all major browsers (including Chrome, Firefox, and Safari) eventually made it de facto mandatory by only supporting HTTP/2 over TLS. This move was intended to prevent 'compression oracle attacks' like CRIME, which targeted the dynamic compression methods used in the older SPDY protocol.

Opens the Intellect+ feed with this card first. Swipe up for the next one.

Sources

  • Summary by Intellect · source: HTTP/2

To cite this card, link to https://intellectplus.co.uk/app/technology-http-2.

How we source, check and correct cards: Editorial standards.

General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.

Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?

Related

Finding something worth knowing…