Merge branch 'cloudflare:production' into production

Author: Thienlta

.windsurf/rules/docs-style-guide.md renamed to .windsurf/rules/general-rules.md

@@ -1,8 +1,38 @@
 ---
-trigger: glob
-globs: *.mdx
+trigger: always_on
 ---
 
+# General rules
+
+## Partial files location
+
+- The partial files used in the docs are located in src/content/partials/
+
+## Partial files variables
+
+- Some partial files have variables to account for the fact that the partials are reused in different places and even products.
+- Some partials also have JSX fragments. These pieces of code are conditionally rendered in the pages where the specific variable (magic word as it's called sometimes) is present. An example of these conditionally rendered pieces of code is:
+
+{ props.magicWord === "hardware" && (
+  <>
+    <p>You need to purchase <a href="https://www.cloudflare.com/magic-wan">{props.productOriginalName}</a> before you can purchase and use the {props.productName}. The {props.productName} can function as your primary edge device for your network, or be deployed in-line with existing network gear.</p>
+  </>
+)
+}
+
+This code would only be rendered if the page has a magicWord variable set to "hardware".
+
+## General guidance
+
+- Do not make any changes to content without showing me what you want to change and asking if I agree to the changes.
+- Do not use HTML for ordered lists.
+- When you use JSX fragments to conditionally render a block of code, always use the props variable to account for the fact that the partials are reused in different places and even products.
+- When you use JSX fragments to conditionally render a block of code, be aware that you will probably need to use the <Markdown /> component to properly render content that is not a single sentence.
+- Only use the <Markdown /> component in JSX conditionals, and only if needed.
+- Do not duplicate content when creating ternary or binary conditions.
+- When adding a variable to a link, use HTML instead of Markdown.
+- Whenever something is not clear, ask the user for more input.
+
 # General styling
 
 - Follow all guidance in the [Cloudflare Style Guide](https://developers.cloudflare.com/style-guide/).
@@ -31,4 +61,4 @@ globs: *.mdx
 - Replace `sh` blocks using `npm commands` with our [`PackageManagers` component](https://developers.cloudflare.com/style-guide/components/package-managers/).
 - Replace in-text mentions of Cloudflare's number of data centers, network capacity, or network peers with our [`PublicStats` component](https://developers.cloudflare.com/style-guide/components/public-stats/).
 - Replace `toml` or `json` code blocks with [Wrangler configuration](https://developers.cloudflare.com/workers/wrangler/configuration/#sample-wrangler-configuration) information with our [`WranglerConfig` component](https://developers.cloudflare.com/style-guide/components/wrangler-config/).
-- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.
+- Replace `ts` or `typescript` code blocks with our [`TypeScriptExample` component](https://developers.cloudflare.com/style-guide/components/typescript-example/). Ignore this rule if the original code block is within a tutorial or other step-by-step guide that is specific to TypeScript.

public/__redirects

@@ -549,6 +549,7 @@
 /dns/reference/troubleshooting/ /dns/reference/recommended-third-party-tools/ 301
 /dns/zone-setups/partial-setup/convert-partial-to-full/ /dns/zone-setups/conversions/convert-partial-to-full/ 301
 /dns/zone-setups/partial-setup/convert-partial-to-secondary/ /dns/zone-setups/conversions/convert-partial-to-secondary/ 301
+/dns/zone-setups/reference/nameserver-assignment/ /dns/nameservers/nameserver-options/#assignment-method 301
 /dns/zone-setups/troubleshooting/dns-probe-finished-nxdomain/ /dns/troubleshooting/dns-probe-finished-nxdomain/ 301
 /dns/zone-setups/troubleshooting/nameservers/ /dns/zone-setups/full-setup/troubleshooting/ 301
 /support/dns/ /dns/ 301

src/components/ResourcesBySelector.tsx

@@ -5,6 +5,7 @@ import ReactSelect from "./ReactSelect";
 import { formatDistance } from "date-fns";
 import { setSearchParams } from "~/util/url";
 import { formatContentType } from "~/util/content-type";
+import Markdown from "react-markdown";
 
 type DocsData = keyof CollectionEntry<"docs">["data"];
 type VideosData = keyof CollectionEntry<"stream">["data"];
@@ -367,7 +368,12 @@ export default function ResourcesBySelector({
 								</p>
 								{showDescriptions && (
 									<span className="line-clamp-3" title={page.data.description}>
-										{page.data.description}
+										<Markdown
+											disallowedElements={["a"]}
+											unwrapDisallowed={true}
+										>
+											{page.data.description}
+										</Markdown>
 									</span>
 								)}
 								{showLastUpdated && "reviewed" in page.data && (

src/content/changelog/cloudflare-tunnel/2025-11-11-cloudflared-proxy-dns.mdx

@@ -0,0 +1,29 @@
+---
+title: cloudflared proxy-dns command will be removed starting February 2, 2026
+description: To address a vulnerability in an underlying library, the `cloudflared proxy-dns` command will be removed from new `cloudflared` releases. Users are advised to migrate to the Cloudflare WARP client or WARP Connector.
+products:
+ - cloudflare-tunnel
+date: 2025-11-11
+---
+
+Starting February 2, 2026, the `cloudflared proxy-dns` command will be removed from all new `cloudflared` [releases](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/).
+
+This change is being made to enhance security and address a potential vulnerability in an underlying DNS library. This vulnerability is specific to the `proxy-dns` command and does not affect any other `cloudflared` features, such as the core [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) service.
+
+The `proxy-dns` command, which runs a client-side [DNS-over-HTTPS (DoH)](/1.1.1.1/encryption/dns-over-https/) proxy, has been an officially undocumented feature for several years. This functionality is fully and securely supported by our actively developed products.
+
+Versions of `cloudflared` released before this date will not be affected and will continue to operate. However, note that our [official support policy](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/#deprecated-releases) for any `cloudflared` release is one year from its release date.
+
+## Migration paths
+
+We strongly advise users of this undocumented feature to migrate to one of the following officially supported solutions before February 2, 2026, to continue benefiting from secure [DNS-over-HTTPS](/1.1.1.1/encryption/dns-over-https/).
+
+### End-user devices
+
+The preferred method for enabling DNS-over-HTTPS on user devices is the [Cloudflare WARP client](/cloudflare-one/team-and-resources/devices/warp/). The WARP client automatically secures and proxies all DNS traffic from your device, integrating it with your organization's [Zero Trust policies](/cloudflare-one/traffic-policies/) and [posture checks](/cloudflare-one/reusable-components/posture-checks/).
+
+### Servers, routers, and IoT devices
+
+For scenarios where installing a client on every device is not possible (such as servers, routers, or IoT devices), we recommend using the [WARP Connector](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/).
+
+Instead of running `cloudflared proxy-dns` on a machine, you can install the WARP Connector on a single Linux host within your private network. This connector will act as a gateway, securely routing all DNS and network traffic from your [entire subnet](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/warp-connector/site-to-internet/) to Cloudflare for [filtering and logging](/cloudflare-one/traffic-policies/).

src/content/changelog/rules/2025-02-12-rules-upgraded-limits.mdx

@@ -8,7 +8,26 @@ date: 2025-02-12
 
 We have upgraded and streamlined [Cloudflare Rules](/rules/) limits across all plans, simplifying rule management and improving scalability for everyone.
 
-**New limits by product:** - [Bulk Redirects](/rules/url-forwarding/bulk-redirects/) - Free: **20** → **10,000** URL redirects across lists - Pro: **500** → **25,000** URL redirects across lists - Business: **500** → **50,000** URL redirects across lists - Enterprise: **10,000** → **1,000,000** URL redirects across lists - [Cloud Connector](/rules/cloud-connector/) - Free: **5** → **10** connectors - Enterprise: **125** → **300** connectors - [Custom Errors](/rules/custom-errors/) - Pro: **5** → **25** error assets and rules - Business: **20** → **50** error assets and rules - Enterprise: **50** → **300** error assets and rules - [Snippets](/rules/snippets/) - Pro: **10** → **25** code snippets and rules - Business: **25** → **50** code snippets and rules - Enterprise: **50** → **300** code snippets and rules - [Cache Rules](/cache/how-to/cache-rules/), [Configuration Rules](/rules/configuration-rules/), [Compression Rules](/rules/compression-rules/), [Origin Rules](/rules/origin-rules/), [Single Redirects](/rules/url-forwarding/single-redirects/), and [Transform Rules](/rules/transform/) - Enterprise: **125** → **300** rules
+**New limits by product:**
+
+- [Bulk Redirects](/rules/url-forwarding/bulk-redirects/)
+  - Free: **20** → **10,000** URL redirects across lists
+  - Pro: **500** → **25,000** URL redirects across lists
+  - Business: **500** → **50,000** URL redirects across lists
+  - Enterprise: **10,000** → **1,000,000** URL redirects across lists
+- [Cloud Connector](/rules/cloud-connector/)
+  - Free: **5** → **10** connectors
+  - Enterprise: **125** → **300** connectors
+- [Custom Errors](/rules/custom-errors/)
+  - Pro: **5** → **25** error assets and rules
+  - Business: **20** → **50** error assets and rules
+  - Enterprise: **50** → **300** error assets and rules
+- [Snippets](/rules/snippets/)
+  - Pro: **10** → **25** code snippets and rules
+  - Business: **25** → **50** code snippets and rules
+  - Enterprise: **50** → **300** code snippets and rules
+- [Cache Rules](/cache/how-to/cache-rules/), [Configuration Rules](/rules/configuration-rules/), [Compression Rules](/rules/compression-rules/), [Origin Rules](/rules/origin-rules/), [Single Redirects](/rules/url-forwarding/single-redirects/), and [Transform Rules](/rules/transform/)
+  - Enterprise: **125** → **300** rules
 
 :::note[Gradual rollout]
 Limits are updated gradually. Some customers may still see previous limits until the rollout is fully completed in the first half of 2025.

src/content/changelog/workers/2025-11-12-analytics-engine-further-sql-enhancements.mdx

@@ -0,0 +1,40 @@
+---
+title: More SQL aggregate, date and time functions available in Workers Analytics Engine
+description: Workers Analytics Engine now supports more SQL functions for aggregation and for working with dates and times
+date: 2025-11-12
+products:
+  - workers-analytics-engine
+---
+You can now perform more powerful queries directly in [Workers Analytics Engine](https://developers.cloudflare.com/analytics/analytics-engine/) with a major expansion of our SQL function library.
+
+Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API. 
+
+Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions: 
+
+[**New aggregate functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/aggregate-functions/)
+- `countIf()` - count the number of rows which satisfy a provided condition
+- `sumIf()` - calculate a sum from rows which satisfy a provided condition
+- `avgIf()` - calculate an average from rows which satisfy a provided condition
+
+[**New date and time functions:**](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/date-time-functions/)
+- `toYear()`
+- `toMonth()`
+- `toDayOfMonth()`
+- `toDayOfWeek()`
+- `toHour()`
+- `toMinute()`
+- `toSecond()`
+- `toStartOfYear()`
+- `toStartOfMonth()`
+- `toStartOfWeek()`
+- `toStartOfDay()`
+- `toStartOfHour()`
+- `toStartOfFifteenMinutes()`
+- `toStartOfTenMinutes()`
+- `toStartOfFiveMinutes()`
+- `toStartOfMinute()`
+- `today()`
+- `toYYYYMM()`
+
+## Ready to get started? 
+Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. [Get started ](/analytics/analytics-engine/get-started/) with Workers Analytics Engine and explore all available functions in our [SQL reference documentation](/analytics/analytics-engine/sql-reference/). 

src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/crawl-pages.mdx

@@ -22,9 +22,9 @@ Once your AI crawler complies with Web Bot Auth, you can begin to crawl webpages
 When an AI crawler makes a request to a page protected by pay per crawl, the server will respond with `HTTP/2 402 Payment Required`. This response will also include the `crawler-price` header which specifies the cost to access the content. For example, a response may look like the following:
 
 ```txt
-HTTP/2 200
+HTTP/2 402
 date: Fri, 06 Jun 2025 08:42:38 GMT
-crawler-charged: USD 0.01
+crawler-price: USD 0.01
 ```
 
 To access this content, the AI crawler must provide headers for paid access.

src/content/docs/analytics/analytics-engine/sql-reference/aggregate-functions.mdx

@@ -248,3 +248,57 @@ SELECT topKWeighted(double1, _sample_interval) FROM my_dataset
 -- find the 15 most common values of <blob1>, weighted by `_sample_interval`
 SELECT topKWeighted(15)(blob1, _sample_interval) FROM my_dataset
 ```
+
+## countIf <Badge text="New" variant="tip" size="small" />
+
+Usage:
+
+```sql
+countIf(<expr>)
+```
+
+`countIf` is an aggregation function that returns the number of rows in the results set,
+but only counting rows where a provided expression evaluates to true.
+
+Example:
+
+```sql
+-- return the number of rows where `double1` is greater than 5
+countIf(double1 > 5)
+```
+
+## sumIf <Badge text="New" variant="tip" size="small" />
+
+Usage:
+
+```sql
+sumIf(<expr>, <expr>)
+```
+
+`sumIf` is an aggregation function that returns the sum of a first expression across all rows in the results set,
+but only including rows where a second expression evaluates to true.
+
+Example:
+
+```sql
+-- return the sum of column `item_cost` of all items where another column `in_stock` is not zero
+sumIf(item_cost, in_stock > 0)
+```
+
+## avgIf <Badge text="New" variant="tip" size="small" />
+
+Usage:
+
+```sql
+avgIf(<expr>, <expr>)
+```
+
+`avgIf` is an aggregation function that returns the mean of an expression across all rows in the results set,
+but only including rows where a second expression evaluates to true.
+
+Example:
+
+```sql
+-- return the mean of column `item_cost` where another column `in_stock` is not zero
+avgIf(item_cost, in_stock > 0)
+```