cloudflare · kodster28 · Mar 24, 2026 · Mar 23, 2026
@@ -6,7 +6,7 @@ products:
 date: 2025-11-19
 ---
 
-[AI Search](/ai-search/) now supports [custom HTTP headers](/ai-search/configuration/data-source/website/#access-protected-content) for website crawling, solving a common problem where valuable content behind authentication or access controls could not be indexed.
+[AI Search](/ai-search/) now supports [custom HTTP headers](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) for website crawling, solving a common problem where valuable content behind authentication or access controls could not be indexed.
 
 Previously, AI Search could only crawl publicly accessible pages, leaving knowledge bases, documentation, and other protected content out of your search results. With custom headers support, you can now include authentication credentials that allow the crawler to access this protected content.
 
@@ -28,4 +28,4 @@ CF-Access-Client-Secret: your-token-secret
 
 The crawler will automatically include these headers in all requests, allowing it to access protected pages that would otherwise be blocked. 
 
-Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#access-protected-content) in AI Search.
+Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search.
@@ -4,7 +4,7 @@ description: HTTP policies can now be configured to send forensic copies for all
 date: 2025-05-07
 ---
 
-You can now [send DLP forensic copies](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#send-http-requests-to-logpush-destination/) to third-party storage for any HTTP policy with an `Allow` or `Block` action, without needing to include a DLP profile. This change increases flexibility for data handling and forensic investigation use cases.
+You can now [send DLP forensic copies](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#send-dlp-forensic-copies-to-logpush-destination) to third-party storage for any HTTP policy with an `Allow` or `Block` action, without needing to include a DLP profile. This change increases flexibility for data handling and forensic investigation use cases.
 
 By default, Gateway will send all matched HTTP requests to your configured DLP Forensic Copy jobs.
 

@@ -24,7 +24,7 @@ To help you apply these topics quickly, we have also released five new predefine
 
 3. **Granular Guardrails**
 
-    You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#application-granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/#ai-prompt-topics) to individual AI applications (for example, ```ChatGPT```) and specific user actions (for example, ```SendPrompt```) to block sensitive prompts.
+    You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/data-loss-prevention/detection-entries/#ai-prompt-topics) to individual AI applications (for example, ```ChatGPT```) and specific user actions (for example, ```SendPrompt```) to block sensitive prompts.
 
     ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
 

@@ -17,4 +17,4 @@ For example, consider a policy that blocks Social Security Numbers (SSNs). Previ
 
 All policies without this selector will continue to scan both request and response bodies to ensure continued protection.
 
-For more information, refer to [Gateway HTTP policy selectors](/cloudflare-one/traffic-policies/http-policies/#body-phase/).
+For more information, refer to [Gateway HTTP policy selectors](/cloudflare-one/traffic-policies/http-policies/#body-phase).
@@ -10,7 +10,7 @@ Use one SaaS integration for Email security to sync with your directory of users
 
 With the other integration, you can have a separate SaaS integration for CASB findings for another SaaS provider.
 
-Refer to [Add an integration](/cloudflare-one/integrations/cloud-and-saas/#add-an-integration) to learn more about this feature.
+Refer to [Add an integration](/cloudflare-one/integrations/cloud-and-saas/) to learn more about this feature.
 
 ![CASB-EmailSecurity](~/assets/images/changelog/email-security/CASB-EmailSecurity.png)
 

@@ -18,4 +18,4 @@ _P50, P75, and P90 Hyperdrive session latency for all client connection sessions
 
 This performance improvement is applied to all new and existing Hyperdrive configurations that have caching enabled.
 
-For more details on how Hyperdrive performs query caching, refer to the [Hyperdrive documentation](/hyperdrive/concepts/how-hyperdrive-works/#query-caching).
+For more details on how Hyperdrive performs query caching, refer to the [Hyperdrive documentation](/hyperdrive/concepts/how-hyperdrive-works/#3-query-caching).
@@ -12,7 +12,7 @@ You can now subscribe to events from other Cloudflare services (for example, [Wo
 
 Event subscriptions allow you to receive messages when events occur across your Cloudflare account. Cloudflare products can publish structured events to a queue, which you can then consume with [Workers](/workers/) or [pull via HTTP from anywhere](/queues/configuration/pull-consumers/).
 
-To create a subscription, use the dashboard or [Wrangler](/workers/wrangler/commands/queues/#subscription-create):
+To create a subscription, use the dashboard or [Wrangler](/workers/wrangler/commands/queues/#queues-subscription-create):
 
 ```bash
 npx wrangler queues subscription create my-queue --source r2 --events bucket.created

@@ -8,7 +8,7 @@ date: 2025-06-10
 
 [Workers Builds](/workers/ci-cd/builds/) connects your Worker to a [Git repository](/workers/ci-cd/builds/git-integration/), and automates building and deploying your code on each pushed change.
 
-To make CI/CD pipelines even more flexible, Workers Builds now automatically injects [default environment variables](/workers/ci-cd/builds/configuration/#environment-variable) into your build process (much like the defaults in [Cloudflare Pages projects](/pages/configuration/build-configuration/#environment-variables)). You can use these variables to customize your build process based on the deployment context, such as the branch or commit.
+To make CI/CD pipelines even more flexible, Workers Builds now automatically injects [default environment variables](/workers/ci-cd/builds/configuration/#environment-variables) into your build process (much like the defaults in [Cloudflare Pages projects](/pages/configuration/build-configuration/#environment-variables)). You can use these variables to customize your build process based on the deployment context, such as the branch or commit.
 
 The following environment variables are injected by default:
 

@@ -37,9 +37,9 @@ When remote bindings are configured, your Worker **still executes locally**, but
 
 **You can try out remote bindings for local development today with:**
 
-- [Wrangler v4.20.3](/workers/development-testing/#using-wrangler-with-remote-bindings): Use the `wrangler dev --x-remote-bindings` command.
-- The [Cloudflare Vite Plugin](/workers/development-testing/#using-vite-with-remote-bindings): Refer to the documentation for how to enable in your Vite config.
-- The [Cloudflare Vitest Plugin](/workers/development-testing/#using-vitest-with-remote-bindings): Refer to the documentation for how to enable in your Vitest config.
+- [Wrangler v4.20.3](/workers/development-testing/#remote-bindings): Use the `wrangler dev --x-remote-bindings` command.
+- The [Cloudflare Vite Plugin](/workers/development-testing/#remote-bindings): Refer to the documentation for how to enable in your Vite config.
+- The [Cloudflare Vitest Plugin](/workers/development-testing/#remote-bindings): Refer to the documentation for how to enable in your Vitest config.
 
 **Have feedback?**
 Join the discussion in our [beta announcement](https://github.com/cloudflare/workers-sdk/discussions/9660) to share feedback or report any issues.
@@ -12,4 +12,4 @@ Workers, including those using [Durable Objects](/durable-objects/) and [Browser
 
 This change allows Workers to handle use cases requiring large message sizes, such as processing Chrome Devtools Protocol messages.
 
-For more information, please see the [Durable Objects startup limits](/durable-objects/platform/limits/#SQLite-backed-Durable-Objects-general-limits).
+For more information, please see the [Durable Objects startup limits](/durable-objects/platform/limits/#sqlite-backed-durable-objects-general-limits).
@@ -6,13 +6,8 @@ products:
   - workers
 ---
 
-
-
 [Workers Builds](/workers/ci-cd/builds/) now supports up to 64 environment variables, and each environment variable can be up to 5 KB in size. The previous limit was 5 KB total across all environment variables.
 
-
-
 This change enables better support for complex build configurations, larger application settings, and more flexible CI/CD workflows.
 
-
-For more details, refer to the [build limits documentation](/workers/ci-cd/builds/limits-and-pricing/#environment-variable-limits).
+For more details, refer to the [build limits documentation](/workers/ci-cd/builds/limits-and-pricing/#definitions).
@@ -24,4 +24,4 @@ To enable Cloudflare Access on your Worker:
 4. For `workers.dev` or Preview URLs, click **Enable Cloudflare Access**.
 5. Optionally, click **Manage Cloudflare Access** to customize the policy.
 
-For more information on configuring Cloudflare Access for Workers, refer to the [Workers Access documentation](/workers/configuration/routing/workers-dev/#cloudflare-access).
+For more information on configuring Cloudflare Access for Workers, refer to the [Workers Access documentation](/workers/configuration/routing/workers-dev/#manage-access-to-workersdev).
@@ -10,7 +10,7 @@ import { WranglerConfig } from "~/components";
 
 You can now configure Workers to run close to infrastructure in legacy cloud regions to minimize latency to existing services and databases. This is most useful when your Worker makes multiple round trips.
 
-To [set a placement hint](/workers/configuration/placement/#use-placement-hints), set the `placement.region` property in your Wrangler configuration file:
+To [set a placement hint](/workers/configuration/placement/#configure-explicit-placement-hints), set the `placement.region` property in your Wrangler configuration file:
 
 <WranglerConfig>
 
@@ -52,7 +52,7 @@ If your existing infrastructure is not in these cloud providers, expose it to pl
 
 </WranglerConfig>
 
-This is an extension of [Smart Placement](/workers/configuration/placement/#use-smart-placement), which automatically places your Workers closer to back-end APIs based on measured latency. When you do not know the location of your back-end APIs or have multiple back-end APIs, set `mode: "smart"`:
+This is an extension of [Smart Placement](/workers/configuration/placement/#enable-smart-placement), which automatically places your Workers closer to back-end APIs based on measured latency. When you do not know the location of your back-end APIs or have multiple back-end APIs, set `mode: "smart"`:
 
 <WranglerConfig>
 

@@ -24,7 +24,7 @@ Both IPv4 and IPv6 addresses are supported.
 
 For zones using [Cloudflare's authoritative DNS](/dns/), Cloudflare typically responds to DNS queries for proxied hostnames with [anycast IPs](/fundamentals/concepts/cloudflare-ip-addresses/). However, if you [customize the IPs Cloudflare uses](/fundamentals/concepts/cloudflare-ip-addresses/#customize-cloudflare-ip-addresses) and use Address Maps, Cloudflare will respond with the IP address(es) on the address map.
 
-Address maps do not change [how Cloudflare reaches the configured origin](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy). The IP addresses defined on your zone's [DNS Records](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) continue to instruct Cloudflare how to reach the origin.
+Address maps do not change [how Cloudflare reaches the configured origin](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy). The IP addresses defined on your zone's [DNS Records](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) continue to instruct Cloudflare how to reach the origin.
 
 :::caution
 Depending on whether you use static IPs or BYOIP, the process to [create an address map](/byoip/address-maps/setup/) is different.

@@ -123,7 +123,7 @@ Make sure you have the correct Key/Token and permissions.
 
 #### DNS records
 
-While the DNS record proxy status and address map will determine how Cloudflare's authoritative DNS responds to requests for your hostnames, the IP addresses specified in `A`/`AAAA` records will determine [how Cloudflare reaches the configured origin](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy).
+While the DNS record proxy status and address map will determine how Cloudflare's authoritative DNS responds to requests for your hostnames, the IP addresses specified in `A`/`AAAA` records will determine [how Cloudflare reaches the configured origin](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy).
 
 :::note
 As you create the necessary DNS records, [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) can help making sure that you have SSL/TLS certificates in place for all your hostnames.

@@ -126,7 +126,7 @@ To create records with the API, use a [POST request](/api/resources/dns/subresou
 As you create the necessary DNS records, [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) can help making sure that you have SSL/TLS certificates in place for all your hostnames.
 :::
 
-While the DNS record proxy status and address map will determine how Cloudflare's authoritative DNS responds to requests for your hostnames, the IP addresses specified in `A`/`AAAA` records will determine [how Cloudflare reaches the configured origin](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy).
+While the DNS record proxy status and address map will determine how Cloudflare's authoritative DNS responds to requests for your hostnames, the IP addresses specified in `A`/`AAAA` records will determine [how Cloudflare reaches the configured origin](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy).
 
 <Details header="Example">
 

@@ -29,7 +29,7 @@ DLP profiles now support setting a [confidence level](/cloudflare-one/data-loss-
 
 **Send entire HTTP requests to a Logpush destination**
 
-In addition to [logging the payload](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-the-payload-of-matched-rules) from HTTP requests that matched a DLP policy in Cloudflare Logs, Enterprise users can now configure a [Logpush job](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#send-http-requests-to-logpush-destination) to send the entire HTTP request that triggered a DLP match to a storage destination. This allows long-term storage of full requests for use in forensic investigation.
+In addition to [logging the payload](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-the-payload-of-matched-rules) from HTTP requests that matched a DLP policy in Cloudflare Logs, Enterprise users can now configure a [Logpush job](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#send-dlp-forensic-copies-to-logpush-destination) to send the entire HTTP request that triggered a DLP match to a storage destination. This allows long-term storage of full requests for use in forensic investigation.
 
 ## 2024-09-03
 

@@ -116,7 +116,7 @@ In addition to detecting and surfacing misconfigurations or issues with SaaS and
 
 ### Configure remediation permissions
 
-Before you can remediate findings, [add a new integration](/cloudflare-one/integrations/cloud-and-saas/#add-an-integration) and choose _Read-Write mode_ during setup. Alternatively, you can update an existing integration:
+Before you can remediate findings, [add a new integration](/cloudflare-one/integrations/cloud-and-saas/) and choose _Read-Write mode_ during setup. Alternatively, you can update an existing integration:
 
 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Cloud & SaaS findings** > **Integrations**.
 2. Choose your integration, then select **Configure**.

@@ -134,7 +134,7 @@ Your new document entry will replace the original document entry. If your file u
 
 ## AI prompt topics
 
-DLP uses [Application Granular Controls](/cloudflare-one/traffic-policies/http-policies/#application-granular-controls) to detect and categorize prompts submitted to generative AI tools. Application Granular Controls analyzes prompts for both content and user intent. Supported AI prompt protection detections include:
+DLP uses [Application Granular Controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls) to detect and categorize prompts submitted to generative AI tools. Application Granular Controls analyzes prompts for both content and user intent. Supported AI prompt protection detections include:
 
 | Detection entry                       | Description                                                                                       |
 | ------------------------------------- | ------------------------------------------------------------------------------------------------- |

@@ -86,7 +86,7 @@ DLP can detect and log the prompt topic sent to an AI tool.
 
 ### Turn on AI prompt content logging for a DLP policy
 
-You can enable payload logging for any Allow or Block HTTP policy that uses the [_Application_](/cloudflare-one/traffic-policies/http-policies/#application) selector with a supported [Application Granular Controls](/cloudflare-one/traffic-policies/http-policies/#application-granular-controls) application.
+You can enable payload logging for any Allow or Block HTTP policy that uses the [_Application_](/cloudflare-one/traffic-policies/http-policies/#application) selector with a supported [Application Granular Controls](/cloudflare-one/traffic-policies/http-policies/#granular-controls) application.
 
 1. Go to **Traffic policies** > **Firewall policies** > **HTTP**.
 2. Edit an existing Allow or Block DLP policy, or [create a new policy](/cloudflare-one/data-loss-prevention/dlp-policies/#2-create-a-dlp-policy).

@@ -18,7 +18,7 @@
 
 <GlossaryDefinition term="Cloudflare Data Loss Prevention (DLP)" />
 
-To prevent interference, Cloudflare does not write scanned content to disk. Instead, DLP only encrypts and temporarily stores content in memory. Optionally, you can configure [payload logging](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-the-payload-of-matched-rules) to store encrypted copies of payloads from matching HTTP requests or a [Logpush destination](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#send-http-requests-to-logpush-destination) to export entire matching HTTP requests.
+To prevent interference, Cloudflare does not write scanned content to disk. Instead, DLP only encrypts and temporarily stores content in memory. Optionally, you can configure [payload logging](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#log-the-payload-of-matched-rules) to store encrypted copies of payloads from matching HTTP requests or a [Logpush destination](/cloudflare-one/data-loss-prevention/dlp-policies/logging-options/#send-dlp-forensic-copies-to-logpush-destination) to export entire matching HTTP requests.
 
 ## Data in transit
 
@@ -47,7 +47,7 @@
 DLP supports reporting and scanning the following file types:

 - Text and CSV
 - Microsoft Office 2007 and later (`.docx`, `.xlsx,` `.pptx`), including Microsoft 365
 - PDF
 - ZIP files containing the above
Original file line number	Diff line number	Diff line change
Expand Up		@@ -17,4 +17,4 @@ For example, consider a policy that blocks Social Security Numbers (SSNs). Previ

		All policies without this selector will continue to scan both request and response bodies to ensure continued protection.

		For more information, refer to [Gateway HTTP policy selectors](/cloudflare-one/traffic-policies/http-policies/#body-phase/).
		For more information, refer to [Gateway HTTP policy selectors](/cloudflare-one/traffic-policies/http-policies/#body-phase).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -18,4 +18,4 @@ _P50, P75, and P90 Hyperdrive session latency for all client connection sessions

		This performance improvement is applied to all new and existing Hyperdrive configurations that have caching enabled.

		For more details on how Hyperdrive performs query caching, refer to the [Hyperdrive documentation](/hyperdrive/concepts/how-hyperdrive-works/#query-caching).
		For more details on how Hyperdrive performs query caching, refer to the [Hyperdrive documentation](/hyperdrive/concepts/how-hyperdrive-works/#3-query-caching).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -12,4 +12,4 @@ Workers, including those using [Durable Objects](/durable-objects/) and [Browser

		This change allows Workers to handle use cases requiring large message sizes, such as processing Chrome Devtools Protocol messages.

		For more information, please see the [Durable Objects startup limits](/durable-objects/platform/limits/#SQLite-backed-Durable-Objects-general-limits).
		For more information, please see the [Durable Objects startup limits](/durable-objects/platform/limits/#sqlite-backed-durable-objects-general-limits).