TLS Certificate Optimization: The Technical Details behind "No Browser Left Behind"
Mar 23, 2016Patrick R. Donahue
Summary
This post details Cloudflare's 'no browser left behind' initiative, specifically focusing on the technical implementation of TLS certificate optimization. It explains the complex logic required to dynamically serve the most appropriate certificate (SHA-1 RSA, SHA-2 RSA, or SHA-2 ECDSA) based on the client's capabilities, as communicated in the TLS ClientHello message. This ensures secure connections for all users, regardless of their browser's support for newer cryptographic standards, while also optimizing for performance.
More from the Website Security & Threat Management trail
- We tested our own WAF with frontier AI models. Here’s what we found
- When scanners miss the attack: how Cloudflare Client-Side Security protects storefronts
- Introducing automatic remediation policies with Cloudflare CASB
- Introducing context-aware vulnerability discovery and remediation with Cloudflare Managed Defense and OpenAI Daybreak Models
- Introducing Adaptive Intelligence: undermining the economics of every bot attack