Skip to content

Commit 3299ad3

Browse files
committed
[SSL/TLS] Remove previously required browser settings change in tls-13.mdx
1 parent ca77acb commit 3299ad3

File tree

1 file changed

+3
-34
lines changed
  • src/content/docs/ssl/edge-certificates/additional-options

1 file changed

+3
-34
lines changed

src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx

Lines changed: 3 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -13,21 +13,21 @@ TLS 1.3 enables the latest version of the TLS protocol (when supported) for impr
1313

1414
TLS 1.3 is the newest, fastest, and most secure version of the TLS protocol. SSL/TLS is the protocol that encrypts communication between users and your website. When web traffic is encrypted with TLS, users will see the green padlock in their browser window.
1515

16-
By turning on the TLS 1.3 feature, traffic to and from your website will be served over the TLS 1.3 protocol when supported by clients. TLS 1.3 protocol has improved latency over older versions, has several new features, and is currently supported in both Chrome (starting with release 66), Firefox (starting with release 60), and in development for Safari and Edge browsers.
16+
By turning on the TLS 1.3 feature, traffic to and from your website will be served over the TLS 1.3 protocol when supported by clients. TLS 1.3 protocol has improved latency over older versions, has several new features, and is currently supported in all updated major browsers.
1717

1818
## Availability
1919

2020
<FeatureTable id="ssl.tls_13" />
2121

2222
## Enable TLS 1.3
2323

24-
TLS 1.3 requires a two-step activation: in the Cloudflare dashboard and in the browser.
24+
TLS 1.3 can be activated in the Cloudflare dashboard or through the API:
2525

2626
### Enable TLS 1.3 in Cloudflare settings
2727

2828
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
2929

30-
To enable TLS 1.3 in the dashboard:
30+
To enable TLS 1.3 in the dashboard.
3131

3232
1. Log in to your [Cloudflare account](https://dash.cloudflare.com) and go to a specific domain.
3333
2. Go to **SSL/TLS** > **Edge Certificates**.
@@ -39,37 +39,6 @@ To adjust your TLS 1.3 settings with the API, send a [`PATCH`](/api/resources/zo
3939

4040
</TabItem> </Tabs>
4141

42-
### Enable TLS 1.3 in the browser
43-
44-
<Details header="Chrome">
45-
46-
1. In the address bar, enter `chrome://flags` and press **Enter**.
47-
2. Scroll to locate the **TLS 1.3 Early Data** entry, and set it to _Enabled_. A message saying that the change will take effect the next time you relaunch Chrome will appear.
48-
3. Select **RELAUNCH NOW** to restart Chrome.
49-
50-
After enabling TLS 1.3, visit a site with TLS 1.3 enabled over HTTPS. Then:
51-
52-
1. Open Chrome **Developer Tools**.
53-
2. Select the **Security** tab.
54-
3. Reload the page (Command-R in macOS, Ctrl-R in Windows).
55-
4. Select the site under **Main origin**.
56-
5. Under **Connection**, confirm that the protocol is **TLS 1.3**.
57-
58-
</Details>
59-
60-
<Details header="Firefox">
61-
62-
1. In the address bar, enter `about:config` and select to accept the warranty warning.
63-
2. Search for `security.tls.version.max` and change the value from `3` (the default) to `4`.
64-
65-
After enabling TLS 1.3, visit a site with TLS 1.3 enabled over HTTPS. Then:
66-
67-
1. Select the lock icon in the address bar.
68-
2. Select **Connection secure** > **More information**.
69-
3. Under **Technical Details**, verify that the TLS version is TLS 1.3.
70-
71-
</Details>
72-
7342
### Troubleshooting
7443

7544
Since TLS 1.3 implementations are relatively new, some failures may occur. If you experience errors, submit a Cloudflare Support ticket with the following information:

0 commit comments

Comments
 (0)