Skip to content

Commit a74ebf1

Browse files
committed
Adds more details to 0-RTT Connection Resumption docs
1 parent d750731 commit a74ebf1

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

src/content/docs/speed/optimization/protocol/0-rtt-connection-resumption.mdx

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,13 @@ sidebar:
77

88
import { FeatureTable, TabItem, Tabs } from "~/components";
99

10-
Zero round trip time resumption (0-RTT) improves performance for clients who have previously connected to your website.
10+
Zero round trip time resumption (0-RTT) improves performance for clients who have previously connected to your website, reducing latency for returning users. This feature is especially beneficial for those who frequently visit your application or connect over mobile networks.
1111

12-
This feature particularly benefits end users who visit your application regularly or who use mobile networks.
12+
We support 0-RTT for GET, HEAD, and OPTIONS requests, facilitating faster responses for these types of requests. Note that 0-RTT is not supported for POST requests.
1313

14-
For more details on what 0-RTT is, how it works, and potential limitations, refer to [our blog](https://blog.cloudflare.com/even-faster-connection-establishment-with-quic-0-rtt-resumption/).
14+
In line with 0-RTT standards, we add the `Early-Data: 1` header to 0-RTT requests, which allows origin servers to identify when a request has used 0-RTT resumption. Customers should be able to see the `Early-Data: 1` header for any 0-RTT requests connecting to their origin.
15+
16+
For more information on 0-RTT, including its functionality and potential limitations, refer to our [blog post](https://blog.cloudflare.com/even-faster-connection-establishment-with-quic-0-rtt-resumption/).
1517

1618
## Availability
1719

0 commit comments

Comments
 (0)