ゆるテックノート

HTTP version history in short

HTTP versions change transport and framing while retaining common method and status semantics. Follow the path from 0.9 to persistent connections, multiplexing, and QUIC. A newer version is not automatically faster in every environment.

Quick timeline

Knowing the milestones helps when designing or debugging.

Key milestones

  • HTTP/0.9 (1991-ish): GET only, no headers, plain HTML.
  • HTTP/1.0 (RFC 1945, 1996): Status lines and headers such as Content-Type. Connections normally close after each exchange, although persistent-connection extensions existed.
  • HTTP/1.1 (RFC 2068, 1997): Persistent connections by default, mandatory Host, and chunked transfer. Current message syntax is RFC 9112, shared semantics RFC 9110, and caching RFC 9111.
  • SPDY (2009): Experimental multiplexing, header compression, prioritization → fed into HTTP/2.
  • HTTP/2 (RFC 7540, 2015; updated by RFC 9113 in 2022): Binary frames multiplexed over TCP, with HPACK header compression.
  • HTTP/3 (RFC 9114, 2022): QUIC over UDP, per-stream delivery, TLS 1.3 protection, and QPACK header compression.

What changed by version

Each revision tackled specific pain points.

HTTP/1.0 → 1.1

  • Persistent connections become the default, reducing connection setup. This does not require a Keep-Alive header on every HTTP/1.1 request.
  • Host header makes virtual hosting practical.
  • Chunked transfer enables streaming-style responses.
  • Cache-Control and ETag clarify caching behavior.

HTTP/1.1 → 2

  • Multiplexing avoids HTTP/1.1 response-order waiting, but TCP packet loss can still stall the entire connection through transport head-of-line blocking.
  • Header compression (HPACK) cuts overhead.
  • The dependency-based priority scheme from RFC 7540 is deprecated in RFC 9113. Priority signals do not guarantee delivery order or speed.
  • Binary framing for extensibility.

HTTP/2 → 3

  • QUIC connection IDs help support network path changes. Migration also depends on configuration and path validation; surviving every network change is not guaranteed.
  • Missing data on one stream does not block delivery of received data on other streams. Ordering within a stream, shared congestion control, and QPACK dependencies can still introduce delays.
  • QPACK adapts header compression to QUIC. HTTP/3 QUIC connections use TLS 1.3 protection. Resumption with 0-RTT has eligibility conditions and replay risks.

Using them today

The version used depends on clients, servers, CDNs, and networks. Check actual connections in developer tools and logs rather than assuming a global adoption figure applies to your site.

Practical notes

  • HTTPS HTTP/2 negotiates h2 with TLS ALPN; HTTP/3 negotiates h3 on a QUIC connection. An endpoint can be discovered through mechanisms such as Alt-Svc. An existing TCP connection does not simply become QUIC.
  • HTTP/3 can be blocked on some networks (UDP). Keep HTTP/2/1.1 as fallback.
  • The Network panel Protocol column can show h2, h3, or http/1.1. With a CDN, browser-to-CDN and CDN-to-origin connections can use different versions.
  • Legacy 1.1 clients remain; servers often serve multiple versions in parallel.
  • Monitor per-version metrics (handshake time, retransmits, QoE) to locate issues.

Takeaway

Separate shared semantics from transport behavior. Continue with data carried by HTTP, method semantics, and understanding transfer speed.

Specifications

HTTP/0.9 / RFC 1945 / SPDY / RFC 9112 / RFC 9113 / RFC 9114 / RFC 9000 / RFC 9001 / RFC 8470