From 628f4c58dd670f0eaa8f73c76fad34332aecbc19 Mon Sep 17 00:00:00 2001 From: Max Phillips Date: Mon, 1 Dec 2025 16:58:33 -0600 Subject: [PATCH] reorder priority --- .../partials/cloudflare-one/gateway/order-of-enforcement.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/partials/cloudflare-one/gateway/order-of-enforcement.mdx b/src/content/partials/cloudflare-one/gateway/order-of-enforcement.mdx index 14767ee105fa542..ee9415dd6d914fd 100644 --- a/src/content/partials/cloudflare-one/gateway/order-of-enforcement.mdx +++ b/src/content/partials/cloudflare-one/gateway/order-of-enforcement.mdx @@ -91,8 +91,8 @@ Gateway applies your policies in the following order: 1. DNS policies with selectors evaluated before resolution 2. Resolver policies (if applicable) 3. DNS policies with selectors evaluated after resolution -4. Network policies -5. Egress policies (if applicable) +4. Egress policies (if applicable) +5. Network policies 6. HTTP policies DNS and resolver policies are standalone. For example, if you block a site with a DNS policy but do not create a corresponding HTTP policy, users can still access the site if they know its IP address.