Gateway - FQDN Filtering For Gateway Egress Policies
1y ago
Source
CloudflareGateway - FQDN Filtering For Gateway Egress Policiescloudflare.comCloudflare One administrators can now control which egress IP is used based on a destination's fully qualified domain name (FDQN) within Gateway Egress policies. Host, Domain, Content Categories, and Application selectors are now available in the Gateway Egress policy builder in beta. 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 . 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.
You might also wanna read
Cloudflare expands AI bot management tools with granular traffic controls for all customers
Cloudflare is celebrating the second "Content Independence Day" by expanding AI traffic management options for all website owners. Building
Workers - Simpler runtime types with @cloudflare/workers-types v5
Cloudflare·2d ago
Workers - Work across multiple accounts with Wrangler auth profiles
Cloudflare·3d ago
Cache - Cache multiple versions of a URL with Vary
Cloudflare·3d ago
Cloudflare One - Hostname routing for Cloudflare Mesh
Cloudflare·3d ago
AI Search - Manage AI Search sync jobs with Wrangler CLI
Cloudflare·3d ago

Comments
Sign in to join the conversation.
No comments yet. Be the first.