Skip to content

Commit 2095375

Browse files
authored
Update 2025-04-28-FDQN-Filtering-Egress-Policies.mdx
adding image for Gateway
1 parent d3853dc commit 2095375

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,5 +11,7 @@ Cloudflare One administrators can now control which egress IP is used based on a
1111
- Host, Domain, Content Categories, and Application selectors are now available in the Gateway Egress policy builder in beta.
1212
- During the beta period, you can use these selectors with traffic on-ramped to Gateway with the WARP client, proxy endpoints (commonly deployed with PAC files), or Cloudflare Browser Isolation.
1313
- For WARP client support, additional configuration is required. For more information, refer to the [WARP client configuration documentation](/cloudflare-one/policies/gateway/egress-policies/#limitations).
14-
14+
15+
!(egress by FQDN and Hostname)[~/src/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview]
16+
1517
This will help apply egress IPs to your users' traffic when an upstream application or network requires it, while the rest of their traffic can take the most performant egress path.

0 commit comments

Comments
 (0)