Skip to content

Commit cc27f90

Browse files
committed
Move mTLS
1 parent 692f328 commit cc27f90

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Gateway does not support TLS decryption for applications which use:
4242
- [ESNI and ECH handshake encryption](#esni-and-ech)
4343
- [Automatic HTTPS upgrades](#google-chrome-automatic-https-upgrades)
4444

45-
### Non-standard ports <Badge text="Beta" variant="caution" size="small" />
45+
### Inspect on all ports <Badge text="Beta" variant="caution" size="small" />
4646

4747
By default, Gateway will only inspect HTTP traffic through port `80`. Additionally, if you turn on TLS decryption, Gateway will inspect HTTPS traffic through port `443`. To detect HTTP and HTTPS traffic on ports other than `80` and `443`, you can turn on [protocol detection](/cloudflare-one/policies/gateway/network-policies/protocol-detection/):
4848

@@ -98,6 +98,10 @@ Chrome Enterprise users can turn off automatic HTTPS upgrades for all URLs with
9898

9999
</TabItem> </Tabs>
100100

101+
### Mutual TLS (mTLS)
102+
103+
When decrypting TLS to inspect traffic, connections that use mutual TLS (mTLS) will fail because Gateway cannot return the necessary client certificate. To prevent connection failures, create a [Do Not Inspect policy](/cloudflare-one/policies/gateway/http-policies/#do-not-inspect) for this traffic.
104+
101105
### ESNI and ECH
102106

103107
Websites that adhere to [ESNI or Encrypted Client Hello (ECH) standards](https://blog.cloudflare.com/encrypted-client-hello/) encrypt the Server Name Indicator (SNI) during the TLS handshake and are therefore incompatible with HTTP inspection. This is because Gateway relies on the SNI to match an HTTP request to a policy. If the ECH fails, browsers will retry the TLS handshake using the unencrypted SNI from the initial request. To avoid this behavior, you can disable ECH in your users' browsers.

src/content/docs/cloudflare-one/policies/gateway/network-policies/protocol-detection.mdx

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,6 @@ You can now use _Detected Protocol_ as a selector in a [Network policy](/cloudfl
2222

2323
By default, Gateway will only inspect HTTP traffic through port `80`. Additionally, if you turn on [TLS decryption](/cloudflare-one/policies/gateway/http-policies/tls-decryption/), Gateway will inspect HTTPS traffic through port `443`. To detect HTTP and HTTPS traffic on ports other than `80` and `443`, under **HTTP inspection ports**, choose _Inspect on all ports_.
2424

25-
:::caution[mTLS limitation]
26-
When inspecting traffic on all ports, connections that use mutual TLS (mTLS) will fail because Gateway cannot return the necessary client certificate. To prevent connection failures, create a [Do Not Inspect policy](/cloudflare-one/policies/gateway/http-policies/#do-not-inspect) for this traffic.
27-
:::
28-
2925
## Supported protocols
3026

3127
Gateway supports detection and filtering of the following protocols:

0 commit comments

Comments
 (0)