Skip to content

HTTP Protocol Evolution: 1.0 to HTTP/3

May 1996 to June 2022.Networking.Standard published.Date precision, month.Evidence grade, primary.5 primary sources

Drivers:

Performance improvementSecurity incidentUser demand

Web page complexity grew from kilobytes to megabytes. Mobile networks exposed latency issues. Security breaches drove HTTPS adoption. Each HTTP version addressed contemporary bottlenecks.

HTTP is the language your browser uses to request web pages. Like human languages, it has evolved over time. Each new version makes websites load faster and more securely. HTTP/2 lets your browser request many things at once; HTTP/3 works better on unreliable mobile connections.

HTTP Protocol Evolution: 1.0 to HTTP/3 event plate

Structured atlas record showing date, domain, evidence grade, source count, and predecessor and successor links.

Event plate: HTTP Protocol Evolution: 1.0 to HTTP/3 Convergence-divergence layout. The central hero card carries the event year, type, title, evidence grade, domain and era band. 0 predecessor cards on the left feed in with red arrows labelled "absorbs". 0 successor cards on the right derive with red arrows labelled "spawns". Key terms below the hero pin the vocabulary the event introduced. EVENT PLATE Source: https://www.rfc-editor.org/rfc/rfc1945 1996 - STANDARD PUBLISHED HTTP Protocol Evolution:1.0 to HTTP/3 primary evidence Domain: AI and machine learning Era band: E6 AI-scale systems KEY TERMS - VOCABULARY THE EVENT INTRODUCED HTTP HTTP/2 HTTP/3 QUIC Convergence-divergence: predecessors absorbed, successors spawned Hero card carries year, evidence and domain. 0 predecessors flow in from the left; 0 successors flow out to the right. Key termsbelow pin the vocabulary the event introduced.

Forecasts and counterfactuals stay labelled as opinion in the event data. Source: Computer History Museum.

Before

The original HTTP/0.9 was extremely simple, supporting only GET requests for HTML. As the Web grew, limitations became apparent: no persistent connections (new TCP connection for each request), no content negotiation, no caching headers, and no security.

What changed

HTTP evolved through multiple versions: HTTP/1.0 (1996) added headers, methods, and status codes; HTTP/1.1 (1999) added persistent connections and chunked transfer; HTTP/2 (2015) added multiplexing and header compression; HTTP/3 (2022) moved to QUIC, eliminating TCP head-of-line blocking.

How it happened

RFC 1945 formalised HTTP/1.0 in 1996. RFC 2616 (HTTP/1.1) addressed performance with persistent connections. Google's SPDY research influenced HTTP/2 (RFC 7540). Cloudflare and Google championed QUIC, leading to HTTP/3 (RFC 9114). Each version maintained backward compatibility while addressing specific performance bottlenecks.

Outcomes

  • Enabled modern web applications with rich interactivity
  • Reduced page load times through multiplexing and compression
  • HTTPS became the default, securing web traffic
  • Mobile web performance improved significantly

Limitations

  • Legacy systems still rely on HTTP/1.1
  • HTTP/2 push feature saw limited adoption
  • QUIC requires UDP, which some networks block
  • Backward compatibility adds protocol complexity

Lessons learnt

  • Incremental improvements sustain long-lived protocols
  • Performance optimisation drives adoption
  • Security should be default, not optional
  • Industry collaboration (browsers, CDNs) accelerates standards

Stakeholders and artefacts

Organisations

  • IETFstandards_bodyHTTP RFC standardisation
  • GooglevendorSPDY and QUIC development
  • W3Cstandards_bodyWeb standards coordination
  • CloudflarevendorQUIC deployment and advocacy

Individuals

  • Roy FieldingCo-author, UC IrvineCo-authored HTTP/1.0 and HTTP/1.1 RFCs, created REST
  • Tim Berners-LeeCo-author, W3COriginal HTTP design, HTTP/1.0 RFC co-author
  • Mike BelsheCo-author, GoogleLed SPDY development, HTTP/2 RFC co-author

Artefacts

  • HTTP/1.1protocolHTTP with persistent connections and chunked transfer
  • HTTP/2protocolBinary protocol with multiplexing and header compression
  • HTTP/3protocolHTTP over QUIC, eliminating head-of-line blocking
  • HTTPSprotocolHTTP secured with TLS encryption

Key terms

HTTPHTTP/2HTTP/3QUICTLSHTTPSmultiplexing

Causality

Preceded by: World Wide Web Invented.

On this course

Read in the path How the Internet Works.

Sources

1Tim Berners-Lee, Roy Fielding, Henrik Frystyk Nielsen. "RFC 1945: Hypertext Transfer Protocol - HTTP/1.0". IETF, 1996-05.authoritativewww.rfc-editor.org/rfc/rfc1945
2Roy Fielding, Jim Gettys, Jeffrey Mogul, Henrik Frystyk Nielsen, Larry Masinter, Paul Leach, Tim Berners-Lee. "RFC 2616: Hypertext Transfer Protocol - HTTP/1.1". IETF, 1999-06.authoritativewww.rfc-editor.org/rfc/rfc2616
3Eric Rescorla. "RFC 2818: HTTP Over TLS". IETF, 2000-05.authoritativewww.rfc-editor.org/rfc/rfc2818
4Mike Belshe, Roberto Peon, Martin Thomson. "RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2)". IETF, 2015-05.authoritativewww.rfc-editor.org/rfc/rfc7540
5Mike Bishop. "RFC 9114: HTTP/3". IETF, 2022-06.authoritativewww.rfc-editor.org/rfc/rfc9114