@@ -41,15 +41,15 @@ Example:
4141 curl --ssl-sessions tls-cache.txt https://example.com
4242
4343The main benefit of --ssl-sessions is a reduction in Time To First Byte
44- (TTFB). In a resumed session, the server does not need to re-send its entire
44+ (* TTFB* ). In a resumed session, the server does not need to re-send its entire
4545certificate chain, which can often be several kilobytes of data. Furthermore,
4646session resumption often requires fewer round-trips than a full handshake.
4747When combined with --tls-earlydata (0-RTT), curl can even send the HTTP
4848request in the first packet of the connection.
4949
5050## Early data
5151
52- The ` --tls-earlydata ` option, is the switch that enables ** TLS 1.3 0-RTT (Zero
52+ The --tls-earlydata option, is the switch that enables ** TLS 1.3 0-RTT (Zero
5353Round Trip Time)** . In a standard TLS handshake, even with version 1.3, there
5454is a back-and-forth exchange before the client can send its actual request
5555(like an HTTP GET). 0-RTT allows a client that has connected to a server
@@ -77,16 +77,16 @@ is a standard security fallback), `curl` will automatically retry the request
7777using a normal handshake, so there is no risk of the connection failing
7878entirely because you used the flag.
7979
80- ## Security and Idempotency
80+ ## Security and idempotency
8181
8282Because 0-RTT data is sent before the full handshake is finalized, it is
8383technically vulnerable to ** replay attacks** . An attacker could capture the
8484early data packet and resend it to the server. For this reason, ` curl ` (and
8585most responsible clients) should only use early data for ** idempotent**
8686requests—those that do not change state on the server, like ` GET ` or ` HEAD ` .
87- You should avoid using ` --tls-earlydata ` with ` POST ` or ` DELETE ` requests
88- unless you are absolutely certain the server has specific protections (like
89- unique tokens or strict replay windows) in place.
87+ You should avoid using --tls-earlydata with ` POST ` or ` DELETE ` requests unless
88+ you are absolutely certain the server has specific protections (like unique
89+ tokens or strict replay windows) in place.
9090
9191## Session tracking
9292
@@ -111,7 +111,7 @@ disable 0-RTT entirely when high levels of anonymity are required.
111111
112112## Requirements
113113
114- To see the benefits of ` --tls-earlydata ` , several stars must align:
114+ To see the benefits of --tls-earlydata, several stars must align:
115115
116116* ** TLS 1.3** : The server and client must both support and negotiate TLS 1.3.
117117
0 commit comments