SSL/TLS Handshake
The negotiation that establishes an encrypted session before any data flows — the round trips behind 'HTTPS feels slow', and why TLS 1.3 cut them.
What is the TLS handshake?
Before any encrypted data moves, client and server run the TLS handshake: agree on a protocol version and cipher suite, authenticate the server via its certificate, and derive shared session keys. Only then does application data flow, symmetrically encrypted. The handshake is where all the interesting cryptography — and all the latency — lives; the session that follows is comparatively cheap.
Why it dominates connection latency
Each handshake round trip is a full network RTT, and they stack on top of TCP’s own handshake. TLS 1.2 needed two RTTs of TLS negotiation; TLS 1.3 cut it to one (and zero for resumed sessions via 0-RTT), which is a major reason modern HTTPS feels faster than a decade ago. To a cross-region endpoint at 100 ms RTT, shaving a round trip is 100 ms off every cold connection — which is precisely why keep-alive connection reuse and session resumption matter so much: they amortize or skip the handshake entirely. Serverless functions that open a fresh TLS connection per invocation pay this tax every time; long-lived pooled connections pay it once.
What the handshake actually secures
Modern suites use ephemeral key exchange (ECDHE) for forward secrecy: session keys are derived per-connection and never transmitted, so even a future compromise of the server’s private key can’t decrypt past captured traffic. Certificate validation during the handshake is what stops impersonation — which is why certificate-validation bugs (accepting expired, self-signed, or wrong-hostname certs) are such serious vulnerabilities: they defeat the handshake’s authentication half while leaving the encryption intact, giving false confidence.
What people get wrong
- Ignoring handshake cost in serverless/microservice designs — per-request connections turn handshake latency into a systemic tax.
- Disabling certificate validation to “fix” a TLS error — that converts encrypted-and-authenticated into encrypted-to-anyone.
- Stuck on TLS 1.2 when 1.3’s single-round-trip handshake is a free latency and security upgrade.
Primary source: RFC 8446 — TLS 1.3
Historical figures and technical concepts for informational purposes only. Not technical, professional, legal, or financial advice. Sources: Official Documentation.