Skip to content

Update 2025-04-28-FDQN-Filtering-Egress-Policies.mdx #22042

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
May 19, 2025
Prev Previous commit
Next Next commit
Update 2025-04-28-FDQN-Filtering-Egress-Policies.mdx
fixing image format
  • Loading branch information
kennyj42 authored Apr 28, 2025
commit 9eeb57c408555632b0b7cfc1ef0f9d77d46d85de
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,6 @@ Cloudflare One administrators can now control which egress IP is used based on a
- 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.
- 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).

!(egress by FQDN and Hostname)[~/src/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview]
![egress by FQDN and Hostname](~/src/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview)

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