Skip to content

Commit 2a4290d

Browse files
ranbelmaxvp
andauthored
Apply suggestions from code review
Co-authored-by: Max Phillips <[email protected]>
1 parent 56759f0 commit 2a4290d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/content/docs/cloudflare-one/policies/gateway/egress-policies/egress-cloudflared.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,18 +88,18 @@ Your private network's CIDR block should also route through the WARP tunnel. For
8888

8989
## 4. (Optional) Configure network policies
9090

91-
You can build [Gateway network policies](/cloudflare-one/policies/gateway/network-policies/) to filter HTTPS traffic to your public hostname on port 443. For example, suppose that you want to block all WARP users from accessing `app.bank.com` except for a specific set of users or groups. Additionally, those authorized users should only access `app.bank.com` using your AWS egress IP. You can accomplish this using two policies: the first allows specific users to reach `app.bank.com`, and the second blocks all other port 443 traffic to `app.bank.com`.
91+
You can build [Gateway network policies](/cloudflare-one/policies/gateway/network-policies/) to filter HTTPS traffic to your public hostname on port `443`. For example, suppose that you want to block all WARP users from accessing `app.bank.com` except for a specific set of users or groups. Additionally, those authorized users should only access `app.bank.com` using your AWS egress IP. You can accomplish this using two policies: the first allows specific users to reach `app.bank.com`, and the second blocks all other port `443` traffic to `app.bank.com`.
9292

93-
1. Allow company employees
93+
1. Allow company employees:
9494
<Render file="gateway/policies/restrict-access-to-private-networks-allow" product="cloudflare-one" params={{ selector: "SNI", value: "app.bank.com" }} />
9595

96-
2. Block everyone else on port 443
96+
2. Block everyone else on port `443`:
9797

9898
| Selector | Operator | Value | Action |
9999
| -------------- | -------- | ------------ | ------ |
100100
| SNI | in | `app.bank.com` | Block |
101101

102-
Gateway does not currently support hostname-based filtering for traffic on non-443 ports. To block traffic to `app.bank.com` on all ports, you will need to use the [Destination IP](/cloudflare-one/policies/gateway/network-policies/#destination-ip) selector and specify the public IP space of `app.bank.com`.
102+
Gateway does not currently support hostname-based filtering for traffic on non-`443` ports. To block traffic to `app.bank.com` on all ports, you will need to use the [Destination IP](/cloudflare-one/policies/gateway/network-policies/#destination-ip) selector and specify the public IP space of `app.bank.com`.
103103

104104
## 5. Test the connection
105105

0 commit comments

Comments
 (0)