How SPDY Paved the Way for QUIC: From HTTP/1.1 to the Future of Web Transport

Previous article summarized HTTP protocol evolution from 1.0 to 2.0; this piece focuses on SPDY, the pioneering predecessor of HTTP/2, and the disruptive QUIC protocol.

1. The Pioneer: SPDY

1. Introduction

SPDY is Google’s improved version of HTTP/1.1 (before HTTP/2 existed). Built on TCP, it addresses many pain points of HTTP/1.x, dramatically speeding up web page loading, and many of its features were later adopted by HTTP/2.

2. Features

Multiplexing

Header compression

Server push

Request prioritization

SPDY architecture diagram

3. Current Status

Before HTTP/2 was released, SPDY already held a notable market share, and for a period both SPDY and HTTP/2 were used side‑by‑side.

2. The Disruptor: QUIC

1. Prerequisite Knowledge

TCP and UDP

TCP (Transmission Control Protocol) is a connection‑oriented, reliable, byte‑stream transport protocol.

Key characteristics of TCP include reliable data delivery, flow control, full‑duplex operation, and support for multiplexed services.

UDP (User Datagram Protocol) is a connection‑less transport protocol that provides simple, unreliable message delivery.

UDP is used for low‑volume, latency‑critical applications such as DNS, NFS, and streaming.

In summary, TCP offers reliable, ordered transmission for large data at the cost of higher latency, while UDP offers fast, unordered transmission for small data.

Diffie‑Hellman Algorithm

The security of the D‑H algorithm relies on the difficulty of the discrete logarithm problem. The exchange proceeds as follows:

(1) Client and server agree on two large primes n and g (public).
(2) Client picks random x, computes A = g^x mod n, sends A.
(3) Server picks random y, computes B = g^y mod n, sends B.
(4) Both compute shared secret K: K = B^x mod n = A^y mod n.
An eavesdropper knowing n, g, A, and B cannot feasibly compute K.

2. What is QUIC?

QUIC is Google’s high‑efficiency, reliable protocol built on UDP. It implements many TCP features while retaining UDP’s low‑latency advantages.

3. Features

a. UDP‑based connection establishment Traditional TCP (and HTTP/2) requires a three‑way handshake plus TLS negotiation, incurring multiple round‑trips. QUIC reduces this to one or two round‑trips, dramatically lowering latency for short‑lived connections.

b. Diffie‑Hellman based encryption Unlike TLS over TCP, which needs multiple round‑trips for key exchange, QUIC uses a DH handshake that establishes a secure channel with a single round‑trip.

Client sends Inchoate Client Hello

Server returns Rejection with public key and config

Client sends Client Hello with its public key

c. Improved multiplexing TCP‑based protocols (HTTP/2, SPDY) still suffer from head‑of‑line blocking because lost packets stall subsequent ones. QUIC’s UDP foundation eliminates this, allowing independent streams without blocking each other.

d. Connection migration QUIC identifies connections by a Connection ID rather than the 4‑tuple (IP, port). Thus, a client can switch between Wi‑Fi and 4G without re‑establishing the connection.

This is especially beneficial for mobile devices that frequently change networks.

e. Negotiation fallback When a client initiates a request, it may open both TCP and QUIC connections. If QUIC wins the race, it is used; otherwise TCP is used. The client marks QUIC as broken if it fails, retrying later.

Client sends TCP request

Server may advertise QUIC via Alt‑Svc header

Client initiates parallel TCP and QUIC connections

Winning connection is used for the request

If QUIC fails, client marks it broken and retries later

Alt‑Svc header example:

Additional QUIC Features

Improved congestion control

Loss recovery

Persistent connections at the transport layer

Head stream ordering guarantees

Two‑level flow control

3. Summary and Reflection

In the evolution of web communication protocols, SPDY was indispensable, dramatically improving page load speed before HTTP/2 and contributing many of its features. QUIC, on the other hand, disrupts TCP by leveraging UDP while preserving TCP‑like reliability, enabling seamless adoption without changing application‑layer semantics. Both innovations originated from Google, underscoring its pivotal role in modern internet transport.

Source: https://segmentfault.com/a/1190000016265991