CloudFlare rolls out support for faster HTTP/2 protocol to all users in effort to spur wider adoption
Russell Brandom / The Verge :
Context & Ripple Effects
HTTP/2 was only finalized earlier this year — the first major rewrite of the protocol in 16 years — and browsers moved first, with Chrome retiring SPDY in favor of HTTP/2. What was missing was server-side scale: most sites couldn't adopt until their infrastructure did.
CloudFlare is closing that gap by switching HTTP/2 on for every customer rather than making it opt-in, which matters because a single CDN decision can flip adoption for millions of sites at once. It also sets up the follow-ons already visible in related coverage: Server Push, encryption defaults, and eventually HTTP/3 support across Cloudflare, Chrome and Firefox.
First-order effects
- Every CloudFlare-hosted site gets HTTP/2 automatically — no configuration, no migration work — so the immediate beneficiaries are its customers' page-load times, not just early adopters who would have enabled it manually.
Second-order effects
- Competing CDNs and hosting providers now face default-on expectations: if CloudFlare ships new protocols to everyone for free, rivals charging for premium performance tiers lose that differentiator.
Third-order effects
- If the pattern holds — and the corpus shows it repeating with TLS 1.3, automatic HTTPS rewrites and opportunistic encryption made default in 2016 — the CDN layer becomes the de facto distribution channel for web standards, with standards bodies effectively relying on CloudFlare-scale operators to make upgrades real.
The trend: Major web protocol upgrades increasingly reach the internet through CDN defaults rather than individual site owners, with CloudFlare turning HTTP/2, then TLS 1.3 and HTTP/3, into network-wide switches.