From ea55bc1ccb620d66f6947444c948024c492b3717 Mon Sep 17 00:00:00 2001 From: Ankur Aggarwal <Encore-Encore@users.noreply.github.com> Date: Mon, 28 Apr 2025 11:19:33 -0700 Subject: [PATCH 1/4] Create 2025-04-28-FDQN-Filtering-Egress-Policies.mdx --- .../2025-04-28-FDQN-Filtering-Egress-Policies.mdx | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx diff --git a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx new file mode 100644 index 000000000000000..41034b1c7bc5a49 --- /dev/null +++ b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx @@ -0,0 +1,15 @@ +--- +title: FQDN Filtering For Gateway Egress Policies +description: Select your egress IP depending on your upstream FQDN, Application, or Category! +products: + - gateway +hidden: false +date: 2025-04-28T11:00:00Z +--- + +Cloudflare One administrators can now control which egress IP is used based on a destination's Fully Qualified Domain Nate (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 this will apply to traffic on-ramped via the WARP client, Proxy Endpoints (commonly deployed via PAC files), or 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). + +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. From 442fcbaa05455add7d354ec5129df100a4a41d50 Mon Sep 17 00:00:00 2001 From: Ankur Aggarwal <Encore-Encore@users.noreply.github.com> Date: Mon, 28 Apr 2025 11:46:35 -0700 Subject: [PATCH 2/4] Update src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx Co-authored-by: Max Phillips <maxvphillips@gmail.com> --- .../gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx index 41034b1c7bc5a49..56ec855d4941c3e 100644 --- a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx +++ b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx @@ -8,8 +8,8 @@ date: 2025-04-28T11:00:00Z --- Cloudflare One administrators can now control which egress IP is used based on a destination's Fully Qualified Domain Nate (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 this will apply to traffic on-ramped via the WARP client, Proxy Endpoints (commonly deployed via PAC files), or Browser Isolation +- 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](/cloudflare-one/policies/gateway/egress-policies/#limitations). 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. From 78ca5a84c37821fae6a3b3acd8e2625bb60ca027 Mon Sep 17 00:00:00 2001 From: Ankur Aggarwal <Encore-Encore@users.noreply.github.com> Date: Mon, 28 Apr 2025 11:46:55 -0700 Subject: [PATCH 3/4] Update src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx Co-authored-by: Max Phillips <maxvphillips@gmail.com> --- .../gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx index 56ec855d4941c3e..1d456dd8613f305 100644 --- a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx +++ b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx @@ -1,6 +1,6 @@ --- title: FQDN Filtering For Gateway Egress Policies -description: Select your egress IP depending on your upstream FQDN, Application, or Category! +description: Select your egress IP depending on your upstream fully qualified domain name (FQDN), application, or category products: - gateway hidden: false From f7e2b148b0c3a2c4c963fe62533b7ad03d507b15 Mon Sep 17 00:00:00 2001 From: Ankur Aggarwal <Encore-Encore@users.noreply.github.com> Date: Mon, 28 Apr 2025 11:47:07 -0700 Subject: [PATCH 4/4] Update src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx Co-authored-by: Max Phillips <maxvphillips@gmail.com> --- .../gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx index 1d456dd8613f305..51b5e0e93ea0249 100644 --- a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx +++ b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx @@ -7,7 +7,7 @@ hidden: false date: 2025-04-28T11:00:00Z --- -Cloudflare One administrators can now control which egress IP is used based on a destination's Fully Qualified Domain Nate (FDQN) within Gateway Egress policies. +Cloudflare 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](/cloudflare-one/policies/gateway/egress-policies/#limitations).