Merge branch 'cloudflare:production' into production

krishnprakash · web-flow · commit 61f76ef8ff7c · 2025-03-06T18:12:53.000+05:30
diff --git a/public/_redirects b/public/_redirects
@@ -252,6 +252,7 @@
 
 # china network
 /support/about-cloudflare/enterprise-documentation/understanding-and-configuring-an-icp-number/ /china-network/concepts/icp/ 301
+/china-network/concepts/china-express/ /china-network/concepts/global-acceleration/ 301
 
 # cloudflare for platforms
 /cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/regional-services-for-saas/ /data-localization/regional-services/get-started/ 301
diff --git a/src/content/docs/1.1.1.1/setup/android.mdx b/src/content/docs/1.1.1.1/setup/android.mdx
@@ -6,6 +6,7 @@ sidebar:
 head:
   - tag: title
     content: Set up 1.1.1.1 on Android
+description: Learn how to set up Cloudflare's 1.1.1.1 DNS resolver on Android devices. Encrypt DNS queries with DoT or DoH, and enable 1.1.1.1 for Families.
 slug: 1.1.1.1/setup/android
 
 ---
@@ -17,7 +18,6 @@ import { Details, Render } from "~/components"
 The app also allows you to enable encryption for DNS queries or enable [WARP mode](/warp-client/), which keeps all your HTTP traffic private and secure, including your DNS queries to 1.1.1.1.
 
 You can select between the options available in the app settings. By default, 1.1.1.1: Faster Internet is configured to WARP mode.
-
 ## Set up 1.1.1.1: Faster Internet
 
 1. Download [1.1.1.1: Faster Internet from Google Play](https://play.google.com/store/apps/details?id=com.cloudflare.onedotonedotonedotone) for free.
diff --git a/src/content/docs/china-network/concepts/china-express.mdx b/src/content/docs/china-network/concepts/china-express.mdx
diff --git a/src/content/docs/china-network/concepts/global-acceleration.mdx b/src/content/docs/china-network/concepts/global-acceleration.mdx
@@ -0,0 +1,60 @@
+---
+title: Global Acceleration
+pcx_content_type: concept
+weight: 4
+---
+
+:::note
+Global Acceleration a service offering that can be an add-on to China Network and also extend Zero Trust services into China.
+:::
+
+Global Acceleration is a suite of connectivity, performance offerings and professional services designed to simplify your global assets' deployment in China. Global Acceleration is provided by our partners including CMI, CBC, and JD Cloud. Depending on what fits your needs best, Global Acceleration can support the following scenarios:
+
+| Offer                                                 | Scenario                                                      |
+| ----------------------------------------------------- | ------------------------------------------------------------- |
+| [CDN Global Acceleration](#cdn-global-acceleration)   | Higher performance of China Network CDN with dynamic content. |
+| [WARP Global Acceleration](#warp-global-acceleration) | WARP client used in China.                                    |
+| [Magic WAN Connection](#mwan-global-acceleration)     | Magic WAN used in China.                                      |
+| [ICP](#icp-services)                                  | ICP services.                                                 |
+| [MLPS](#mlps-services)                                | MLPS certification services.                                  |
+| [Travel SIM](#travel-sim)                             | Zero Trust clients in business traveling to China.            |
+
+## CDN Global Acceleration
+
+CDN Global Acceleration provides stable and reliable connections for dynamic content entering and exiting China, specifically beneficial for users' experience within the country. Additionally, this service can help facilitate seamless dynamic traffic management, ensuring stable connectivity across multiple global origins. It can support more advanced scenarios of Cloudflare features with great performance, such as accessing Cloudflare R2 and Cloudflare Fonts in China.
+
+## WARP Global Acceleration
+
+WARP Global Acceleration is a verified solution for enabling WARP client access within China, allowing remote employees to maintain secure and consistent connections.
+
+## Magic WAN Global Acceleration
+
+Magic WAN Global Acceleration is a verified solution for enabling Magic WAN access within China, allowing in-office employees to maintain secure and reliable connectivity.
+
+## ICP services
+
+Internet Content Provider (ICP) service simplifies the complexities of acquiring an ICP for domains to operate compliantly within China.
+
+## MLPS services
+
+The Multi-Level Protection Scheme (MLPS) service add-on streamlines the certification process to secure the MLPS L3 certification for your applications.
+
+### Travel SIM
+
+Travel SIM offers temporary, seamless WARP access for individual employees traveling to China, ensuring uninterrupted connectivity during their visit.
+
+---
+
+## General process
+
+### 1. Validate prerequisites
+
+Ensure that you have a Cloudflare [Enterprise plan](https://www.cloudflare.com/plans/enterprise/) and [China Network](/china-network/) if you want CDN Global Acceleration or other offers. Licenses of WARP and Magic WAN are required for WARP Connection or Magic WAN Global Acceleration.
+
+### 2. Sign contract
+
+Contact your Cloudflare account team. They will assist you with contracting with our local China partners.
+
+### 3. Deploy Global Acceleration
+
+Our local China partners will assist you to deploy Global Acceleration.
diff --git a/src/content/docs/china-network/index.mdx b/src/content/docs/china-network/index.mdx
@@ -22,13 +22,12 @@ The Cloudflare China Network provides:
 - An unified experience for managing network traffic and security posture. You can manage all configurations on the same dashboard.
 - The same customer support capabilities as Cloudflare's global network. You may also have access to premium service and local language support.
 - [In-China Authoritative DNS and in-China nameservers](/china-network/concepts/china-dns/) to improve the Time to First Byte (TTFB) performance.
-- [China Express](/china-network/concepts/china-express) is a suite of connectivity, performance offerings and professional services designed to simplify your global assets' deployment in China.
+- [Global Acceleration](/china-network/concepts/global-acceleration/) is a suite of connectivity, performance offerings and professional services designed to simplify your global assets' deployment in China.
 
 ### Video Introduction
 
 <Stream id="b7933a5b3636ca29f834128ca92665b3" title="China Network Overview" thumbnail="1s" />
 
-
 ## Availability
 
 The Cloudflare China Network is available as a separate subscription for customers on an [Enterprise plan](https://www.cloudflare.com/plans/enterprise/).
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/office365-api.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/api/office365-api.mdx
@@ -5,6 +5,8 @@ sidebar:
   order: 3
 ---
 
+import { Render } from "~/components"
+
 This guide will instruct you through setting up Microsoft Office 365 with Email Security via the Cloudflare dashboard.
 
 ## Prerequisites
@@ -73,4 +75,8 @@ To view the integration for each connected domain:
 1. Select a domain.
 2. Select the three dots > **View integration**.
 
-Once you have set up Email Security to scan through your inbox, Email Security will display detailed information about your inbox. Refer to [Monitor your inbox](/cloudflare-one/email-security/email-monitoring/) to learn more.
+Once you have set up Email Security to scan through your inbox, Email Security will display detailed information about your inbox. Refer to [Monitor your inbox](/cloudflare-one/email-security/email-monitoring/) to learn more.
+
+## Next steps
+
+<Render file="email-security/enable-logs" />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/bcc-microsoft-exchange.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/bcc-microsoft-exchange.mdx
@@ -73,4 +73,8 @@ If you have multiple rules, you may need to change the order of the BCC rule and
 
 ## Email processing and reports
 
-In BCC mode, all emails are put through automated phishing detections by Email Security. Emails that trigger phishing detections are logged for reporting via product portal, email and Slack. Emails that do not trigger any detections are deleted.
+In BCC mode, all emails are put through automated phishing detections by Email Security. Emails that trigger phishing detections are logged for reporting via product portal, email and Slack. Emails that do not trigger any detections are deleted.
+
+## Next steps
+
+<Render file="email-security/enable-logs" />
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/enable-gmail-integration.mdx
@@ -84,4 +84,7 @@ Enter the email associated with the Google Workspace Administrator account. Your
 
 ## Next steps
 
-Now that you have created an integration, you will need to [connect your domains](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains/) for Email Security to start scanning your inbox.
+Now that you have created an integration:
+
+- [Connect your domains](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/connect-domains/) for Email Security to start scanning your inbox.
+- [Enable logs](/cloudflare-one/insights/logs/enable-logs/) to send detection data to an endpoint of your choice.
diff --git a/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/office365-journaling.mdx b/src/content/docs/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/office365-journaling.mdx
@@ -5,7 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip, Render } from "~/components"
 
 When you receive an email, the email lands on your Microsoft O365 inbox, and then Email Security receives a copy of that email. The following email flow shows how this works:
 
@@ -51,4 +51,8 @@ Your domains are now added successfully.
 To view your connected domains:
 
 1. Go to **Settings**.
-2. Locate your domain, select the three dots > **View domain**. Selecting **View domain** will display information about your domain.
+2. Locate your domain, select the three dots > **View domain**. Selecting **View domain** will display information about your domain.
+
+## Next steps
+
+<Render file="email-security/enable-logs" />
diff --git a/src/content/docs/dns/concepts.mdx b/src/content/docs/dns/concepts.mdx
@@ -45,7 +45,7 @@ In this context, you can have a primary DNS setup, when you use Cloudflare to ma
 
 When you have a primary DNS setup, you can either use only Cloudflare (also known as [Full setup](/dns/zone-setups/full-setup/)), or you can use Cloudflare and another provider, where the other provider is the one to receive [outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/) from Cloudflare.
 
-Finally, as Cloudflare also works as a [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy), [partial (CNAME) setups](/dns/zone-setups/partial-setup/) can be used when you do not want Cloudflare to be [authoritative](#authoritative-dns) for your domain but you still want to proxy individual subdomains through Cloudflare.
+Finally, as Cloudflare also works as a [reverse proxy](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy), [partial (CNAME) setups](/dns/zone-setups/partial-setup/) can be used when you do not want Cloudflare to be [authoritative](#authoritative-dns) for your domain but you still want to proxy individual subdomains through Cloudflare.
 
 ## DNS records
 
diff --git a/src/content/docs/dns/dns-firewall/faq.mdx b/src/content/docs/dns/dns-firewall/faq.mdx
@@ -1,6 +1,7 @@
 ---
 title: FAQ
 pcx_content_type: faq
+description: Find answers to common questions about Cloudflare's DNS Firewall, including cache behavior, EDNS support, and setting PTR records.
 sidebar:
   order: 4
 head:
diff --git a/src/content/docs/dns/dns-firewall/random-prefix-attacks/about.mdx b/src/content/docs/dns/dns-firewall/random-prefix-attacks/about.mdx
@@ -7,6 +7,7 @@ head:
   - tag: title
     content: About random prefix attacks - DNS Firewall
 
+description: Learn about random prefix attacks. As part of DNS Firewall, Cloudflare can protect your upstream authoritative nameservers from these attacks.
 ---
 
 import { Render } from "~/components"
diff --git a/src/content/docs/dns/get-started.mdx b/src/content/docs/dns/get-started.mdx
@@ -23,7 +23,7 @@ Once the setup is completed:
 
 - You [manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) through the Cloudflare dashboard or API. This is how you control which resources are available on the apex domain (`example.com`) or specific subdomains (`blog.example.com`) of your website, as well as control other configurations.
 
-- Cloudflare [responds to all DNS queries](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-dns-provider) for your hostnames and your DNS records are propagated across the [Cloudflare global network](https://www.cloudflare.com/network/), speeding up your domain.
+- Cloudflare [responds to all DNS queries](/fundamentals/concepts/how-cloudflare-works/) for your hostnames and your DNS records are propagated across the [Cloudflare global network](https://www.cloudflare.com/network/), speeding up your domain.
 
 ## Resources
 
diff --git a/src/content/docs/magic-transit/how-to/configure-static-routes.mdx b/src/content/docs/magic-transit/how-to/configure-static-routes.mdx
@@ -22,7 +22,6 @@ import { Render } from "~/components"
 		trafficSteering: "/magic-transit/reference/traffic-steering/",
 		magicWANecmp: " ",
 		createPath: "Magic Transit > Configuration",
-		tunnelEndpoints: "/magic-transit/how-to/configure-tunnels/",
-		ipRanges: " "
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnels/"
 	}}
 />
diff --git a/src/content/docs/magic-wan/configuration/manually/how-to/configure-static-routes.mdx b/src/content/docs/magic-wan/configuration/manually/how-to/configure-static-routes.mdx
@@ -15,14 +15,14 @@ import { Render } from "~/components"
 	file="static-routes"
 	product="magic-transit"
 	params={{
+		magicProduct: "Magic WAN",
 		productName: "Magic WAN",
 		BGPpath: "/magic-wan/configuration/manually/how-to/bgp-peering/",
 		anycastURL: "/magic-wan/reference/tunnels/",
 		trafficSteering: "/magic-wan/reference/traffic-steering/",
 		magicWANecmp: "The maximum number of routes you can have with the same priority is 64.",
 		createPath: "Magic WAN > Configuration",
-		tunnelEndpoints: "/magic-wan/configuration/manually/how-to/configure-tunnels/",
-		ipRanges: "<br /> When using Magic WAN and Cloudflare Tunnel together, remember to consider the IP ranges utilized in the static routes of Cloudflare Tunnel when selecting static routes for Magic WAN. For more information, refer to [Cloudflare Tunnel](/magic-wan/zero-trust/cloudflare-tunnel/). <p></p>"
+		tunnelEndpoints: "/magic-wan/configuration/manually/how-to/configure-tunnels/"
 	}}
 />
 
diff --git a/src/content/docs/rules/snippets/create-dashboard.mdx b/src/content/docs/rules/snippets/create-dashboard.mdx
@@ -13,20 +13,24 @@ import { Render } from "~/components";
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and website.
 
-2. Go to **Rules** > **Snippets**, and select **Create a Snippet**.
+2. Go to **Rules** > **Snippets**.
 
-3. In **Snippet name**, enter a descriptive name for the snippet. You cannot change the name after creating the snippet.
+3. (Optional) If you have not created any snippets yet, select one of the snippet templates that addresses a common use case. Then, review and adjust the proposed snippet code.
 
-4. Enter the snippet's JavaScript code in the code editor. You can test how your snippet will handle incoming requests using the **HTTP** and **Preview** tabs.
+   To start from scratch, select **Create Snippet**.
 
-5. Select **Snippet rule** to configure when the snippet will run.
+4. In **Snippet name**, enter a descriptive name for the snippet. You cannot change the name after creating the snippet.
 
-6. Under **Run this Snippet if incoming requests match**, select if you wish to run the snippet only for requests that match a custom filter expression or for all incoming requests.
+5. Enter the snippet's JavaScript code in the code editor. You can test how your snippet will handle incoming requests using the **HTTP** and **Preview** tabs.
 
-7. (Optional) To define a custom expression, use the Expression Builder (specifying one or more values for **Field**, **Operator**, and **Value**) or manually enter an expression using the Expression Editor. For more information, refer to [Edit expressions in the dashboard](/ruleset-engine/rules-language/expressions/edit-expressions/).
+6. Select **Snippet rule** to configure when the snippet will run.
 
-8. Select **Done**.
+7. Under **Run this Snippet if incoming requests match**, select if you wish to run the snippet only for requests that match a custom filter expression or for all incoming requests.
 
-9. To deploy your snippet, select **Deploy**. If you are not ready to deploy your snippet, open the dropdown next to **Deploy** and select **Save as Draft**.
+8. (Optional) To define a custom expression, use the Expression Builder (specifying one or more values for **Field**, **Operator**, and **Value**) or manually enter an expression using the Expression Editor. For more information, refer to [Edit expressions in the dashboard](/ruleset-engine/rules-language/expressions/edit-expressions/).
 
-   <Render file="rules-creation-dash-dns-popup" />
+9. Select **Done**.
+
+10. To deploy your snippet, select **Deploy**. If you are not ready to deploy your snippet, open the dropdown next to **Deploy** and select **Save as Draft**.
+
+    <Render file="rules-creation-dash-dns-popup" />
diff --git a/src/content/docs/rules/snippets/index.mdx b/src/content/docs/rules/snippets/index.mdx
diff --git a/src/content/docs/rules/transform/managed-transforms/reference.mdx b/src/content/docs/rules/transform/managed-transforms/reference.mdx
diff --git a/src/content/partials/cloudflare-one/email-security/enable-logs.mdx b/src/content/partials/cloudflare-one/email-security/enable-logs.mdx
diff --git a/src/content/partials/magic-transit/static-routes.mdx b/src/content/partials/magic-transit/static-routes.mdx
diff --git a/src/content/partials/workers/storage_api_pricing.mdx b/src/content/partials/workers/storage_api_pricing.mdx
