TLS Session Resumption
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://statuscodefyi.com/iframe/glossary/tls-resumption/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://statuscodefyi.com/glossary/tls-resumption/
Add a dynamic SVG badge to your README or docs.
[](https://statuscodefyi.com/glossary/tls-resumption/)
Use the native HTML custom element.
Mechanisms that allow a client to skip the full TLS handshake when reconnecting to a server it has previously established a session with. TLS 1.2 supports two methods: session IDs (server stores session state) and session tickets (server encrypts state and gives it to the client). TLS 1.3 replaces both with PSK (Pre-Shared Key) resumption via session tickets, combined with optional 0-RTT data in the first flight. Resumption reduces handshake latency from 1-RTT to 0-RTT at the cost of a replay risk for 0-RTT data.