Skip to content

Commit f9c6649

Browse files
authored
[Gateway] Clarify H3 behavior (#22564)
1 parent 38ae1d3 commit f9c6649

File tree

1 file changed

+7
-9
lines changed
  • src/content/docs/cloudflare-one/policies/gateway/http-policies

1 file changed

+7
-9
lines changed

src/content/docs/cloudflare-one/policies/gateway/http-policies/http3.mdx

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -22,43 +22,41 @@ To enable HTTP/3 inspection, turn on the [Gateway proxy](/cloudflare-one/policie
2222

2323
### Application limitations
2424

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.
2626

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.
2828

2929
## Force HTTP/2 traffic
3030

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.
3232

3333
<Details header="Google Chrome">
3434

3535
1. Go to `chrome://flags`
36-
2. Disable **Experimental QUIC protocol**.
36+
2. Set **Experimental QUIC protocol** to _Disabled_.
3737
3. Relaunch Chrome.
3838

3939
</Details>
4040

4141
<Details header="Safari">
4242

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.
4644

4745
</Details>
4846

4947
<Details header="Firefox">
5048

5149
1. Go to `about:config`.
5250
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_.
5452
4. Relaunch Firefox.
5553

5654
</Details>
5755

5856
<Details header="Microsoft Edge">
5957

6058
1. Go to `edge://flags`
61-
2. Disable **Experimental QUIC protocol**.
59+
2. Set **Experimental QUIC protocol** to _Disabled_.
6260
3. Relaunch Edge.
6361

6462
</Details>

0 commit comments

Comments
 (0)