Merge branch 'cloudflare:production' into production

krishnprakash · web-flow · commit 16e61cae99ba · 2025-02-26T18:36:03.000+05:30
diff --git a/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx b/src/content/docs/analytics/account-and-zone-analytics/zone-analytics.mdx
@@ -51,7 +51,6 @@ These metrics include legitimate user requests as well as crawlers and threats.
 
 * **Web Traffic** - Displays metrics for *Requests*, *Bandwidth*, and *Unique Visitors*. If you are using Cloudflare Workers, subrequests data will not be visible in zone Traffic Analytics. Instead, you can find subrequests analytics under the **Workers & Pages** tab in the **Overview** section. Refer to [Worker Analytics](/analytics/account-and-zone-analytics/analytics-with-workers/#worker-analytics) for more information.
 * **Web Traffic Requests by Country** - Is an interactive map that breaks down the number of requests by country.  This panel also includes a data table for **Top Traffic Countries / Regions** that display the countries with the most number of requests (up to five, if the data exists).
-* **Share Your Stats -** Lets you share actual site statistics on social media (Twitter) for: *Bytes saved,* *SSL requests served*, and *attacks blocked*.
 
 #### Pro, Business, or Enterprise plan
 
diff --git a/src/content/docs/cache/how-to/cache-rules/create-dashboard.mdx b/src/content/docs/cache/how-to/cache-rules/create-dashboard.mdx
@@ -8,6 +8,8 @@ head:
     content: Create a cache rule in the dashboard
 ---
 
+import { Render } from "~/components";
+
 1.  Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
 2.  Go to **Rules** > **Overview**.
 3.  Next to **Cache Rules**, select **Create rule**.
@@ -41,3 +43,5 @@ head:
 11. Under **Place at**, from the dropdown, you can select the order of your rule. From the main page, you can also change the order of the rules you have created.
 
 12. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+
+    <Render file="rules-creation-dash-dns-popup" product="rules" />
diff --git a/src/content/docs/images/transform-images/index.mdx b/src/content/docs/images/transform-images/index.mdx
@@ -10,7 +10,7 @@ import { Render } from "~/components"
 
 Transformations let you optimize and manipulate images stored outside of the Cloudflare Images product. Transformed images are served from one of your zones on Cloudflare.
 
-To transform an image, you must [enable transformations for your zone](/images/get-started/#enable-transformations).
+To transform an image, you must [enable transformations for your zone](/images/get-started/#enable-transformations-on-your-zone).
 
 You can transform an image by using a [specially-formatted URL](/images/transform-images/transform-via-url/) or [through Workers](/images/transform-images/transform-via-workers/).
 
diff --git a/src/content/docs/logs/R2-log-retrieval.mdx b/src/content/docs/logs/R2-log-retrieval.mdx
@@ -12,7 +12,7 @@ Logs Engine gives you the ability to store your logs in R2 and query them direct
 
 :::note
 
-Logs Engine is going to be replaced by Log Explorer. For further details, consult the [Log Explorer](/logs/log-explorer/) documentation and to request access, complete the [sign-up form](https://cloudflare.com/lp/log-explorer/). 
+Logs Engine is going to be replaced by Log Explorer. For further details, consult the [Log Explorer](/logs/log-explorer/) documentation and to request access, complete the [sign-up form](https://cloudflare.com/lp/log-explorer/).
 :::
 
 ## Store logs in R2
@@ -81,7 +81,7 @@ Stream logs stored in R2 that match the provided query parameters, using the end
 ```bash
 curl --globoff "https://api.cloudflare.com/client/v4/accounts/{account_id}/logs/retrieve?start=2022-06-01T16:00:00Z&end=2022-06-01T16:05:00Z&bucket=cloudflare-logs&prefix=http_requests/example.com/{DATE}" \
 --header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \ 
+--header "X-Auth-Key: <API_KEY>" \
 --header "R2-Access-Key-Id: R2_ACCESS_KEY_ID" \
 --header "R2-Secret-Access-Key: R2_SECRET_ACCESS_KEY"
 ```
diff --git a/src/content/docs/logs/get-started/alerts-and-analytics.mdx b/src/content/docs/logs/get-started/alerts-and-analytics.mdx
@@ -46,7 +46,7 @@ query
         datetime_gt:"2022-08-15T00:00:00Z",
         destinationType:"s3",
         status_neq:200
-      }, 
+      },
       limit:10)
       {
         count,
diff --git a/src/content/docs/logs/get-started/enable-destinations/datadog.mdx b/src/content/docs/logs/get-started/enable-destinations/datadog.mdx
@@ -183,10 +183,10 @@ Response:
 
 :::note[Note]
 
-The Datadog destination is exclusive to new jobs and might not be backward compatible with older jobs. Create new jobs if you expect to send your logs directly to Datadog instead of modifying already existing ones. If you try to modify an existing job for another destination to push logs to Datadog, you may observe errors. 
+The Datadog destination is exclusive to new jobs and might not be backward compatible with older jobs. Create new jobs if you expect to send your logs directly to Datadog instead of modifying already existing ones. If you try to modify an existing job for another destination to push logs to Datadog, you may observe errors.
 :::
 
 :::note[Note]
 
-To analyze and visualize Cloudflare metrics using the Cloudflare Integration tile for Datadog, follow the steps in the [Datadog Analytics integration page](/analytics/analytics-integrations/datadog/). 
+To analyze and visualize Cloudflare metrics using the Cloudflare Integration tile for Datadog, follow the steps in the [Datadog Analytics integration page](/analytics/analytics-integrations/datadog/).
 :::
diff --git a/src/content/docs/logs/get-started/enable-destinations/google-cloud-storage.mdx b/src/content/docs/logs/get-started/enable-destinations/google-cloud-storage.mdx
@@ -57,5 +57,5 @@ To enable Logpush to GCS:
 
 :::note[Note]
 
-To analyze your Cloudflare Logs data using the Google Cloud Platform (GCP), follow the steps in the [Google Cloud Analytics integration page](/analytics/analytics-integrations/google-cloud/). 
+To analyze your Cloudflare Logs data using the Google Cloud Platform (GCP), follow the steps in the [Google Cloud Analytics integration page](/analytics/analytics-integrations/google-cloud/).
 :::
diff --git a/src/content/docs/logs/get-started/enable-destinations/http.mdx b/src/content/docs/logs/get-started/enable-destinations/http.mdx
@@ -13,7 +13,7 @@ Cloudflare Logpush now supports the ability to send logs to configurable HTTP en
 Note that when using Logpush to HTTP endpoints, Cloudflare customers are expected to perform their own authentication of the pushed logs. For example, customers may specify a secret token in the URL or an HTTP header of the Logpush destination.
 
 :::note[Endpoint requirements]
-Cloudflare expects that the endpoint is available over HTTPS, using a trusted certificate. The endpoint must accept `POST` requests. 
+Cloudflare expects that the endpoint is available over HTTPS, using a trusted certificate. The endpoint must accept `POST` requests.
 :::
 
 ## Manage via the Cloudflare dashboard
@@ -62,7 +62,7 @@ The supported parameters are as follows:
 
 :::note[Note]
 
-The `ownership_challenge` parameter is not required to create a Logpush job to an HTTP endpoint. You need to make sure that the file upload to validate the destination accepts a gzipped `test.txt.gz` with content as `{"content":"tests"}` compressed, otherwise it will return an error, like `error validating destination: error writing object: error uploading`. 
+The `ownership_challenge` parameter is not required to create a Logpush job to an HTTP endpoint. You need to make sure that the file upload to validate the destination accepts a gzipped `test.txt.gz` with content as `{"content":"tests"}` compressed, otherwise it will return an error, like `error validating destination: error writing object: error uploading`.
 
 :::
 
diff --git a/src/content/docs/logs/get-started/enable-destinations/ibm-cloud-logs.mdx b/src/content/docs/logs/get-started/enable-destinations/ibm-cloud-logs.mdx
@@ -9,7 +9,7 @@ head:
 
 ---
 
-Cloudflare Logpush supports pushing logs directly to IBM Cloud Logs via API. The dashboard functionality will later be added. 
+Cloudflare Logpush supports pushing logs directly to IBM Cloud Logs via API. The dashboard functionality will later be added.
 
 ## Manage via API
 
@@ -25,7 +25,7 @@ Ensure Log Share permissions are enabled, before attempting to read or configure
 ### 1. Create a job
 
 To create a job, make a `POST` request to the Logpush jobs endpoint with the following fields:
-    
+
 - **name** (optional) - Use your domain name as the job name.
 - **output_options** (optional) - This parameter is used to define the desired output format and structure. Below are the configurable fields:
     - output_type
diff --git a/src/content/docs/logs/get-started/enable-destinations/new-relic.mdx b/src/content/docs/logs/get-started/enable-destinations/new-relic.mdx
@@ -63,7 +63,7 @@ To create a job, make a `POST` request to the Logpush jobs endpoint with the fol
 
   :::note[Note]
 
-  To query Cloudflare logs, New Relic requires fields to be sent as a Unix Timestamp. 
+  To query Cloudflare logs, New Relic requires fields to be sent as a UNIX timestamp.
 
   :::
 
@@ -176,6 +176,6 @@ Response:
 
 :::note[Note]
 
-To analyze and visualize Cloudflare metrics using the Cloudflare Network Logs quickstart, follow the steps in the [New Relic Analytics integration page](/analytics/analytics-integrations/new-relic/). 
+To analyze and visualize Cloudflare metrics using the Cloudflare Network Logs quickstart, follow the steps in the [New Relic Analytics integration page](/analytics/analytics-integrations/new-relic/).
 
 :::
diff --git a/src/content/docs/logs/get-started/enable-destinations/r2.mdx b/src/content/docs/logs/get-started/enable-destinations/r2.mdx
@@ -67,7 +67,7 @@ To create a job, make a `POST` request to the Logpush jobs endpoint with the fol
 
 :::note[Note]
 
-We recommend adding the `{DATE}` parameter in the `destination_conf` to separate your logs into daily subfolders. 
+We recommend adding the `{DATE}` parameter in the `destination_conf` to separate your logs into daily subfolders.
 :::
 
 ```bash
diff --git a/src/content/docs/logs/get-started/enable-destinations/s3-compatible-endpoints.mdx b/src/content/docs/logs/get-started/enable-destinations/s3-compatible-endpoints.mdx
@@ -107,7 +107,7 @@ curl https://api.cloudflare.com/client/v4/zones/{zone_id}/logpush/jobs \
   "output_options": {
     "field_names": ["ClientIP", "ClientIP", "ClientRequestHost", "ClientRequestMethod", "ClientRequestURI","EdgeEndTimestamp", "EdgeResponseBytes", "EdgeResponseStatus", "EdgeStartTimestamp", "RayID"],
     "timestamp_format": "rfc3339"
-  },  
+  },
   "dataset": "http_requests"
 }'
 ```
diff --git a/src/content/docs/logs/get-started/enable-destinations/sumo-logic.mdx b/src/content/docs/logs/get-started/enable-destinations/sumo-logic.mdx
@@ -56,5 +56,5 @@ To enable Logpush to Sumo Logic:
 
 * Sumo Logic may impose throttling and caps on your log ingestion to prevent your account from using **On-Demand Capacity**. Refer to [manage ingestion](https://help.sumologic.com/docs/manage/ingestion-volume/log-ingestion/).
 
-* To analyze and visualize Cloudflare Logs using the Cloudflare App for Sumo Logic, follow the steps in the Sumo Logic integration documentation to [install the Cloudflare App](https://help.sumologic.com/docs/integrations/saas-cloud/cloudflare/#installing-the-cloudflare-app) and [view the Cloudflare dashboards](https://help.sumologic.com/docs/integrations/saas-cloud/cloudflare/#viewing-the-cloudflare-dashboards). 
+* To analyze and visualize Cloudflare Logs using the Cloudflare App for Sumo Logic, follow the steps in the Sumo Logic integration documentation to [install the Cloudflare App](https://help.sumologic.com/docs/integrations/saas-cloud/cloudflare/#installing-the-cloudflare-app) and [view the Cloudflare dashboards](https://help.sumologic.com/docs/integrations/saas-cloud/cloudflare/#viewing-the-cloudflare-dashboards).
   :::
diff --git a/src/content/docs/logs/index.mdx b/src/content/docs/logs/index.mdx
@@ -13,7 +13,7 @@ import { CardGrid, Description, Feature, LinkTitleCard, RelatedProduct } from "~
 
 <Description>
 
-Detailed logs that contain metadata generated by our products. 
+Detailed logs that contain metadata generated by our products.
 </Description>
 
 These logs are helpful for debugging, identifying configuration adjustments, and creating analytics, especially when combined with logs from other sources, such as your application server. For information about the types of data Cloudflare collects, refer to [Cloudflare's Types of analytics](/analytics/types-of-analytics/).
@@ -48,11 +48,11 @@ Use Logs Engine to store your logs in R2 and query them directly.
 ## Related products
 
 <RelatedProduct header="Audit Logs" href="/fundamentals/setup/account/account-security/review-audit-logs/" product="fundamentals">
-Summarize the history of changes made within your Cloudflare account. 
+Summarize the history of changes made within your Cloudflare account.
 </RelatedProduct>
 
 <RelatedProduct header="Web Analytics" href="/web-analytics/" product="analytics">
-Provides privacy-first analytics without changing your DNS or using Cloudflare's proxy. 
+Provides privacy-first analytics without changing your DNS or using Cloudflare's proxy.
 </RelatedProduct>
 
 ***
diff --git a/src/content/docs/logs/log-explorer.mdx b/src/content/docs/logs/log-explorer.mdx
@@ -45,7 +45,7 @@ Note that these permissions exist at the account and zone level and you need the
 
 Authentication with the API can be done via an authentication header or API token. Append your API call with either of the following additional parameters.
 
-- **Authentication header** 
+- **Authentication header**
 
   - `X-Auth-Email` - the Cloudflare account email address associated with the domain
   - `X-Auth-Key` - the Cloudflare API key
@@ -54,11 +54,11 @@ Authentication with the API can be done via an authentication header or API toke
 
   - `Authorization: Bearer <API_TOKEN>` To create an appropriately scoped API token, refer to [Create API token](/fundamentals/api/get-started/create-token/) documentation. Copy and paste the token into the authorization parameter for your API call.
 
-    
+
 
 ## Enable Log Explorer
 
-In order for Log Explorer to begin storing logs, you need to enable the desired datasets. You can do this via the dashboard or the API. 
+In order for Log Explorer to begin storing logs, you need to enable the desired datasets. You can do this via the dashboard or the API.
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
diff --git a/src/content/docs/magic-network-monitoring/faq.mdx b/src/content/docs/magic-network-monitoring/faq.mdx
@@ -6,6 +6,14 @@ sidebar:
   order: 11
 ---
 
+Below you will find answers to our most commonly asked questions. If you cannot find the answer you are looking for, refer to the [community page](https://community.cloudflare.com/) to explore more resources.
+
+## I am getting an "Invalid account settings request body: account name format contains illegal characters or is not supported" error when trying to create a rule.
+
+This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
+
+Refer to [Account name](/fundamentals/setup/account/customize-account/account-name/) to learn how to change your account name.
+
 ## Can I send NetFlow/sFlow data to Cloudflare in a secure, encrypted way?
 
 Yes. Both enterprise and free customers can send encrypted network flow data to Cloudflare.
diff --git a/src/content/docs/magic-network-monitoring/rules/index.mdx b/src/content/docs/magic-network-monitoring/rules/index.mdx
@@ -2,12 +2,24 @@
 title: Rules
 pcx_content_type: how-to
 sidebar:
+  label: Manage rules
   order: 4
 
 ---
 
 Magic Network Monitoring rules will allow you to monitor the traffic volume destined for IP addresses or IP prefixes on your network. You can also receive alerts if the volume of traffic arriving at specific destinations exceeds a defined threshold.
 
+:::caution[Invalid account settings error when trying to create a rule]
+If you get the following error when trying to create a rule:
+
+`Invalid account settings request body: account name format contains illegal characters or is not supported`
+
+Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
+
+Refer to [Account name](/fundamentals/setup/account/customize-account/account-name/) to learn how to change your account name.
+:::
+
+
 ## Create rules
 
 Refer to [Recommended rule configuration](/magic-network-monitoring/rules/recommended-rule-configuration/) for more details on the settings we recommend to create appropriate Magic Network Monitoring rules.
diff --git a/src/content/docs/r2/buckets/create-buckets.mdx b/src/content/docs/r2/buckets/create-buckets.mdx
@@ -48,4 +48,3 @@ wrangler r2 bucket delete BUCKET_TO_DELETE
 
 - Bucket names and buckets are not public by default. To allow public access to a bucket, [visit the public bucket documentation](/r2/buckets/public-buckets/).
 - Invalid (unauthorized) access attempts to private buckets do not incur R2 operations charges against that bucket. Refer to the [R2 pricing FAQ](/r2/pricing/#frequently-asked-questions) to understand what operations are billed vs. not billed.
-- The TLS (SSL) certificate created for each R2 bucket uses a wildcard certificate of the form `*.r2.cloudflarestorage.com`, which prevents account IDs and names from showing up in Certificate Transparency logs.
diff --git a/src/content/docs/rules/cloud-connector/create-dashboard.mdx b/src/content/docs/rules/cloud-connector/create-dashboard.mdx
@@ -8,6 +8,8 @@ head:
     content: Configure a Cloud Connector rule in the dashboard
 ---
 
+import { Render } from "~/components";
+
 To configure a Cloud Connector rule in the dashboard:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
@@ -34,4 +36,6 @@ To configure a Cloud Connector rule in the dashboard:
 
    Alternatively, select **All incoming requests** to redirect all incoming traffic for your zone to the storage bucket you selected.
 
-To save and deploy your rule, select **Deploy**. If you are not ready to deploy the rule, select **Save as Draft**.
+7. To save and deploy your rule, select **Deploy**. If you are not ready to deploy the rule, select **Save as Draft**.
+
+   <Render file="rules-creation-dash-dns-popup" />
diff --git a/src/content/docs/rules/compression-rules/create-dashboard.mdx b/src/content/docs/rules/compression-rules/create-dashboard.mdx
@@ -8,6 +8,8 @@ head:
     content: Create a compression rule in the dashboard
 ---
 
+import { Render } from "~/components";
+
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Go to **Rules** > **Overview**.
 3. Select **Create rule** > **Compression Rule**.
@@ -17,3 +19,5 @@ head:
 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 rule expressions](/ruleset-engine/rules-language/expressions/edit-expressions/).
 8. Under **Compression options**, set the [compression options](/rules/compression-rules/settings/#dashboard-configuration-settings).
 9. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+
+   <Render file="rules-creation-dash-dns-popup" />
diff --git a/src/content/docs/rules/configuration-rules/create-dashboard.mdx b/src/content/docs/rules/configuration-rules/create-dashboard.mdx
@@ -8,6 +8,8 @@ head:
     content: Create a configuration rule in the dashboard
 ---
 
+import { Render } from "~/components";
+
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Go to **Rules** > **Overview**.
 3. Select **Create rule** > **Configuration Rule**.
@@ -17,3 +19,5 @@ head:
 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/).
 8. Under **Then the settings are**, add the [configuration settings](/rules/configuration-rules/settings/) you wish to change for requests matching the rule expression.
 9. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+
+   <Render file="rules-creation-dash-dns-popup" />
diff --git a/src/content/docs/rules/origin-rules/create-dashboard.mdx b/src/content/docs/rules/origin-rules/create-dashboard.mdx
@@ -8,6 +8,8 @@ head:
     content: Create an origin rule in the dashboard
 ---
 
+import { Render } from "~/components";
+
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
 2. Go to **Rules** > **Overview**.
 3. Select **Create rule** > **Origin Rule**.
@@ -16,3 +18,5 @@ head:
 6. Under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/).
 7. Under **Set origin parameters**, define the [origin rule settings](/rules/origin-rules/features/) you wish to change for requests matching the rule expression.
 8. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+
+   <Render file="rules-creation-dash-dns-popup" />
diff --git a/src/content/docs/rules/page-rules/manage.mdx b/src/content/docs/rules/page-rules/manage.mdx
diff --git a/src/content/docs/rules/reference/troubleshooting.mdx b/src/content/docs/rules/reference/troubleshooting.mdx
diff --git a/src/content/docs/rules/snippets/create-dashboard.mdx b/src/content/docs/rules/snippets/create-dashboard.mdx
diff --git a/src/content/docs/rules/transform/request-header-modification/create-dashboard.mdx b/src/content/docs/rules/transform/request-header-modification/create-dashboard.mdx
diff --git a/src/content/docs/rules/transform/response-header-modification/create-dashboard.mdx b/src/content/docs/rules/transform/response-header-modification/create-dashboard.mdx
diff --git a/src/content/docs/rules/transform/url-rewrite/create-dashboard.mdx b/src/content/docs/rules/transform/url-rewrite/create-dashboard.mdx
diff --git a/src/content/docs/rules/url-forwarding/bulk-redirects/create-dashboard.mdx b/src/content/docs/rules/url-forwarding/bulk-redirects/create-dashboard.mdx
diff --git a/src/content/docs/rules/url-forwarding/single-redirects/create-dashboard.mdx b/src/content/docs/rules/url-forwarding/single-redirects/create-dashboard.mdx
diff --git a/src/content/partials/rules/rules-creation-dash-dns-popup.mdx b/src/content/partials/rules/rules-creation-dash-dns-popup.mdx
diff --git a/src/content/partials/workers/wrangler-commands/global-flags.mdx b/src/content/partials/workers/wrangler-commands/global-flags.mdx

Original file line number	Diff line number	Diff line change
`@@ -46,7 +46,7 @@ query`
`46`	`46`	`datetime_gt:"2022-08-15T00:00:00Z",`
`47`	`47`	`destinationType:"s3",`
`48`	`48`	`status_neq:200`
`49`		`- },`
	`49`	`+ },`
`50`	`50`	`limit:10)`
`51`	`51`	`{`
`52`	`52`	`count,`