You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/policies/gateway/http-policies/http3.mdx
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,43 +22,41 @@ To enable HTTP/3 inspection, turn on the [Gateway proxy](/cloudflare-one/policie
22
22
23
23
### Application limitations
24
24
25
-
Gateway can inspect HTTP/3 traffic from Mozilla Firefox and Microsoft Edge, as well as other HTTP applications, such as cURL.
25
+
Gateway can inspect HTTP/3 traffic from Mozilla Firefox and Microsoft Edge by establishing an HTTP/3 proxy connection. Gateway will then terminate the HTTP/3 connection, decrypt and inspect the traffic, and connect to the destination server over HTTP/2. Gateway can also inspect other HTTP applications, such as cURL.
26
26
27
-
If the UDP proxy is enabled in Zero Trust, Google Chrome will force all HTTP/3 traffic to fall back to HTTP/2, allowing you to enforce your HTTP policies. If the UDP proxy is not enabled, HTTP/3 traffic from Chrome will bypass inspection.
27
+
If the UDP proxy is turned on in Zero Trust, Google Chrome will cancel all HTTP/3 connections and retry them with HTTP/2, allowing you to enforce your HTTP policies. If the UDP proxy is turned off, HTTP/3 traffic from Chrome will bypass inspection.
28
28
29
29
## Force HTTP/2 traffic
30
30
31
-
To apply Gateway policies to HTTP traffic without turning on the UDP proxy, you must disable QUIC in your users' browsers to ensure only HTTP/2 traffic reaches Gateway.
31
+
To apply Gateway policies to HTTP traffic without turning on the UDP proxy, you must turn off QUIC in your users' browsers to ensure only HTTP/2 traffic reaches Gateway.
32
32
33
33
<Detailsheader="Google Chrome">
34
34
35
35
1. Go to `chrome://flags`
36
-
2.Disable**Experimental QUIC protocol**.
36
+
2.Set**Experimental QUIC protocol** to _Disabled_.
37
37
3. Relaunch Chrome.
38
38
39
39
</Details>
40
40
41
41
<Detailsheader="Safari">
42
42
43
-
1. Go to **Safari** > **Settings** > **Advanced** and enable **Show Develop menu in menu bar**, then relaunch Safari.
44
-
2. Go to **Develop** > **Experimental Features** and disable **HTTP/3**.
45
-
3. Relaunch Safari.
43
+
You cannot turn off QUIC in Safari. All traffic will be sent over HTTP/3.
46
44
47
45
</Details>
48
46
49
47
<Detailsheader="Firefox">
50
48
51
49
1. Go to `about:config`.
52
50
2. If you receive a warning, select **Accept the Risk and Continue**.
53
-
3.Disable**network.http.http3.enable**.
51
+
3.Set**network.http.http3.enable** to _false_.
54
52
4. Relaunch Firefox.
55
53
56
54
</Details>
57
55
58
56
<Detailsheader="Microsoft Edge">
59
57
60
58
1. Go to `edge://flags`
61
-
2.Disable**Experimental QUIC protocol**.
59
+
2.Set**Experimental QUIC protocol** to _Disabled_.
0 commit comments