From 5900b91383c4f201dc457aab48f7016ed2fc4afb Mon Sep 17 00:00:00 2001 From: "ask-bonk[bot]" Date: Mon, 23 Mar 2026 18:58:28 +0000 Subject: [PATCH] fix: repair broken anchor links across docs and changelogs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fix broken header anchor links identified by the anchor link audit workflow run #138. Changes include: - WARP → Cloudflare One Client renames (#proxy-mode → #local-proxy-mode, #gateway-with-doh → #dns-only-mode, #switch-organizations-in-warp → #switch-organizations-in-the-cloudflare-one-client, etc.) - Wrangler command page anchor prefix updates (pages/#dev-1 → #pages-dev, queues/#subscription-create → #queues-subscription-create, etc.) - Heading rename fixes (#query-caching → #3-query-caching, #application-granular-controls → #granular-controls, etc.) - Case sensitivity fix (#SQLite-backed → #sqlite-backed) - Trailing slash removal (#body-phase/ → #body-phase) - Removed anchors to non-existent sections Closes #29240 --- ...19-add-extra-headers-for-website-crawling.mdx | 4 ++-- .../dlp/2025-05-07-forensic-copy-update.mdx | 2 +- .../dlp/2025-08-25-ai-prompt-protection.mdx | 2 +- .../dlp/2025-09-25-body-phase-selector.mdx | 2 +- .../2025-04-01-casb-email-security.mdx | 2 +- .../2024-12-11-hyperdrive-caching-at-edge.mdx | 2 +- .../queues/2025-08-19-event-subscriptions.mdx | 2 +- .../workers/2025-06-10-default-env-vars.mdx | 2 +- .../workers/2025-06-18-remote-bindings-beta.mdx | 6 +++--- ...31-increased-websocket-message-size-limit.mdx | 2 +- .../2025-11-21-builds-env-var-increase.mdx | 7 +------ .../2025-12-03-reusable-access-policies.mdx | 2 +- .../2026-01-22-explicit-placement-hints.mdx | 4 ++-- src/content/docs/byoip/address-maps/index.mdx | 2 +- .../byoip/service-bindings/cdn-and-spectrum.mdx | 2 +- .../service-bindings/magic-transit-with-cdn.mdx | 2 +- .../docs/cloudflare-one/changelog/dlp.mdx | 2 +- .../cloud-and-saas-findings/manage-findings.mdx | 2 +- .../data-loss-prevention/detection-entries.mdx | 2 +- .../dlp-policies/logging-options.mdx | 2 +- .../data-loss-prevention/index.mdx | 2 +- .../integrations/cloud-and-saas/openai.mdx | 2 +- .../docs/d1/configuration/data-location.mdx | 2 +- src/content/docs/d1/get-started.mdx | 2 +- src/content/docs/d1/sql-api/sql-statements.mdx | 2 +- src/content/docs/kv/index.mdx | 2 +- src/content/docs/pages/functions/bindings.mdx | 16 ++++++++-------- .../pages/functions/debugging-and-logging.mdx | 4 ++-- src/content/docs/pages/functions/get-started.mdx | 2 +- .../docs/pages/functions/local-development.mdx | 4 ++-- src/content/docs/pages/functions/source-maps.mdx | 4 ++-- .../docs/pages/get-started/direct-upload.mdx | 8 ++++---- ...direct-upload-with-continuous-integration.mdx | 4 ++-- .../build-an-api-with-pages-functions.mdx | 2 +- .../how-it-works/egress-ips.mdx | 2 +- .../docs/workers/ci-cd/builds/build-branches.mdx | 4 ++-- .../migration-guides/migrate-from-pages.mdx | 4 ++-- .../docs/workers/wrangler/configuration.mdx | 2 +- .../docs/workers/wrangler/deprecations.mdx | 2 +- .../hyperdrive/planetscale-placement-partial.mdx | 2 +- src/content/release-notes/hyperdrive.yaml | 2 +- .../warp-releases/linux/beta/2025.10.118.1.yaml | 2 +- .../warp-releases/linux/beta/2025.7.106.1.yaml | 4 ++-- .../warp-releases/linux/ga/2025.10.186.0.yaml | 2 +- .../warp-releases/linux/ga/2025.7.176.0.yaml | 4 ++-- .../warp-releases/linux/ga/2025.8.779.0.yaml | 4 ++-- .../warp-releases/macos/beta/2025.10.118.1.yaml | 2 +- .../warp-releases/macos/beta/2025.7.106.1.yaml | 4 ++-- .../warp-releases/macos/ga/2025.10.186.0.yaml | 2 +- .../warp-releases/macos/ga/2025.7.176.0.yaml | 4 ++-- .../warp-releases/macos/ga/2025.8.779.0.yaml | 4 ++-- .../windows/beta/2025.10.118.1.yaml | 2 +- .../warp-releases/windows/beta/2025.2.460.1.yaml | 2 +- .../warp-releases/windows/beta/2025.7.106.1.yaml | 4 ++-- .../warp-releases/windows/ga/2025.10.186.0.yaml | 2 +- .../warp-releases/windows/ga/2025.2.600.0.yaml | 2 +- .../warp-releases/windows/ga/2025.7.176.0.yaml | 4 ++-- .../warp-releases/windows/ga/2025.8.779.0.yaml | 4 ++-- .../warp-releases/windows/ga/2025.9.558.0.yaml | 2 +- 59 files changed, 88 insertions(+), 93 deletions(-) diff --git a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx index 66e9932b8e4..5a9abdb9296 100644 --- a/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx +++ b/src/content/changelog/ai-search/2025-11-19-add-extra-headers-for-website-crawling.mdx @@ -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. \ No newline at end of file +Learn more about [configuring custom headers for website crawling](/ai-search/configuration/data-source/website/#extra-headers-for-access-protected-content) in AI Search. \ No newline at end of file diff --git a/src/content/changelog/dlp/2025-05-07-forensic-copy-update.mdx b/src/content/changelog/dlp/2025-05-07-forensic-copy-update.mdx index cea9629060d..8e1919ec234 100644 --- a/src/content/changelog/dlp/2025-05-07-forensic-copy-update.mdx +++ b/src/content/changelog/dlp/2025-05-07-forensic-copy-update.mdx @@ -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. diff --git a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx index 072bd9362de..be224c5214d 100644 --- a/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx +++ b/src/content/changelog/dlp/2025-08-25-ai-prompt-protection.mdx @@ -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) diff --git a/src/content/changelog/dlp/2025-09-25-body-phase-selector.mdx b/src/content/changelog/dlp/2025-09-25-body-phase-selector.mdx index 5ad892beb64..cb7025a0d50 100644 --- a/src/content/changelog/dlp/2025-09-25-body-phase-selector.mdx +++ b/src/content/changelog/dlp/2025-09-25-body-phase-selector.mdx @@ -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). diff --git a/src/content/changelog/email-security-cf1/2025-04-01-casb-email-security.mdx b/src/content/changelog/email-security-cf1/2025-04-01-casb-email-security.mdx index 171ec114c25..d46c4e7bcbe 100644 --- a/src/content/changelog/email-security-cf1/2025-04-01-casb-email-security.mdx +++ b/src/content/changelog/email-security-cf1/2025-04-01-casb-email-security.mdx @@ -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) diff --git a/src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx b/src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx index 2a402131c91..4c512738d8c 100644 --- a/src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx +++ b/src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx @@ -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). diff --git a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx index fcbfb52680d..cd3df4c25c1 100644 --- a/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx +++ b/src/content/changelog/queues/2025-08-19-event-subscriptions.mdx @@ -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 diff --git a/src/content/changelog/workers/2025-06-10-default-env-vars.mdx b/src/content/changelog/workers/2025-06-10-default-env-vars.mdx index e5b5b2cb972..22e7f111d52 100644 --- a/src/content/changelog/workers/2025-06-10-default-env-vars.mdx +++ b/src/content/changelog/workers/2025-06-10-default-env-vars.mdx @@ -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: diff --git a/src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx b/src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx index 337da969c67..8c80d6d5bcb 100644 --- a/src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx +++ b/src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx @@ -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. diff --git a/src/content/changelog/workers/2025-10-31-increased-websocket-message-size-limit.mdx b/src/content/changelog/workers/2025-10-31-increased-websocket-message-size-limit.mdx index 8f1d3d6b087..07ee3b1f03a 100644 --- a/src/content/changelog/workers/2025-10-31-increased-websocket-message-size-limit.mdx +++ b/src/content/changelog/workers/2025-10-31-increased-websocket-message-size-limit.mdx @@ -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). diff --git a/src/content/changelog/workers/2025-11-21-builds-env-var-increase.mdx b/src/content/changelog/workers/2025-11-21-builds-env-var-increase.mdx index 9b953e7fff3..cde7fd3e867 100644 --- a/src/content/changelog/workers/2025-11-21-builds-env-var-increase.mdx +++ b/src/content/changelog/workers/2025-11-21-builds-env-var-increase.mdx @@ -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). \ No newline at end of file +For more details, refer to the [build limits documentation](/workers/ci-cd/builds/limits-and-pricing/#definitions). diff --git a/src/content/changelog/workers/2025-12-03-reusable-access-policies.mdx b/src/content/changelog/workers/2025-12-03-reusable-access-policies.mdx index d8223752f4f..5738addaaaa 100644 --- a/src/content/changelog/workers/2025-12-03-reusable-access-policies.mdx +++ b/src/content/changelog/workers/2025-12-03-reusable-access-policies.mdx @@ -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). diff --git a/src/content/changelog/workers/2026-01-22-explicit-placement-hints.mdx b/src/content/changelog/workers/2026-01-22-explicit-placement-hints.mdx index 2aee37be836..0a0872007e4 100644 --- a/src/content/changelog/workers/2026-01-22-explicit-placement-hints.mdx +++ b/src/content/changelog/workers/2026-01-22-explicit-placement-hints.mdx @@ -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: @@ -52,7 +52,7 @@ If your existing infrastructure is not in these cloud providers, expose it to pl -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"`: diff --git a/src/content/docs/byoip/address-maps/index.mdx b/src/content/docs/byoip/address-maps/index.mdx index 02f895b37cd..9885f3dd32f 100644 --- a/src/content/docs/byoip/address-maps/index.mdx +++ b/src/content/docs/byoip/address-maps/index.mdx @@ -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. diff --git a/src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx b/src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx index 343774f38e8..b3b7f792c5e 100644 --- a/src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx +++ b/src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx @@ -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. diff --git a/src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx b/src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx index cc52b2d8626..1fdc384e00b 100644 --- a/src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx +++ b/src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx @@ -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).
diff --git a/src/content/docs/cloudflare-one/changelog/dlp.mdx b/src/content/docs/cloudflare-one/changelog/dlp.mdx index 612c8940970..a51a0725002 100644 --- a/src/content/docs/cloudflare-one/changelog/dlp.mdx +++ b/src/content/docs/cloudflare-one/changelog/dlp.mdx @@ -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 diff --git a/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx b/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx index 3b52e4540c2..03cf5a34a8f 100644 --- a/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx +++ b/src/content/docs/cloudflare-one/cloud-and-saas-findings/manage-findings.mdx @@ -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**. diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries.mdx index 8fe0e092f5d..47e2f31bb99 100644 --- a/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries.mdx +++ b/src/content/docs/cloudflare-one/data-loss-prevention/detection-entries.mdx @@ -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 | | ------------------------------------- | ------------------------------------------------------------------------------------------------- | diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-policies/logging-options.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-policies/logging-options.mdx index 6fdaa1e2b5d..10611e0fc0c 100644 --- a/src/content/docs/cloudflare-one/data-loss-prevention/dlp-policies/logging-options.mdx +++ b/src/content/docs/cloudflare-one/data-loss-prevention/dlp-policies/logging-options.mdx @@ -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). diff --git a/src/content/docs/cloudflare-one/data-loss-prevention/index.mdx b/src/content/docs/cloudflare-one/data-loss-prevention/index.mdx index 6378f07d8dd..ede4ff460ee 100644 --- a/src/content/docs/cloudflare-one/data-loss-prevention/index.mdx +++ b/src/content/docs/cloudflare-one/data-loss-prevention/index.mdx @@ -18,7 +18,7 @@ Users on Zero Trust Free and Pay-as-you-go plans can use the [Financial Informat -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 diff --git a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/openai.mdx b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/openai.mdx index 2a7c67a392b..691a3cf5ac9 100644 --- a/src/content/docs/cloudflare-one/integrations/cloud-and-saas/openai.mdx +++ b/src/content/docs/cloudflare-one/integrations/cloud-and-saas/openai.mdx @@ -40,7 +40,7 @@ Compliance API access is required to use the OpenAI CASB integration. To enable - The name of the user who created the key - The requested scope (`read`, `write`, or both) 2. OpenAI will verify the key and grant the requested Compliance API scopes. -3. After the scopes are granted, [add the OpenAI integration to CASB](/cloudflare-one/integrations/cloud-and-saas/#add-an-integration). When prompted, enter your Open AI Admin API key, Organization ID, and Workspace ID (available at `https://chatgpt.com/admin/settings`). +3. After the scopes are granted, [add the OpenAI integration to CASB](/cloudflare-one/integrations/cloud-and-saas/). When prompted, enter your Open AI Admin API key, Organization ID, and Workspace ID (available at `https://chatgpt.com/admin/settings`). For more information, refer to the [OpenAI Help Center](https://help.openai.com/articles/9261474-compliance-api-for-enterprise-customers). diff --git a/src/content/docs/d1/configuration/data-location.mdx b/src/content/docs/d1/configuration/data-location.mdx index f69680778ba..c38400217f4 100644 --- a/src/content/docs/d1/configuration/data-location.mdx +++ b/src/content/docs/d1/configuration/data-location.mdx @@ -68,7 +68,7 @@ You may want to explicitly provide a location hint in cases where the majority o Provide a location hint when creating a D1 database when: -- Using [`wrangler d1`](/workers/wrangler/commands/d1/#d1) to create a database. +- Using [`wrangler d1`](/workers/wrangler/commands/d1/) to create a database. - Creating a database [via the Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers/d1). :::caution diff --git a/src/content/docs/d1/get-started.mdx b/src/content/docs/d1/get-started.mdx index a8e55295229..91996d98af8 100644 --- a/src/content/docs/d1/get-started.mdx +++ b/src/content/docs/d1/get-started.mdx @@ -640,6 +640,6 @@ In this tutorial, you have: If you have any feature requests or notice any bugs, share your feedback directly with the Cloudflare team by joining the [Cloudflare Developers community on Discord](https://discord.cloudflare.com). -- See supported [Wrangler commands for D1](/workers/wrangler/commands/d1/#d1). +- See supported [Wrangler commands for D1](/workers/wrangler/commands/d1/). - Learn how to use [D1 Worker Binding APIs](/d1/worker-api/) within your Worker, and test them from the [API playground](/d1/worker-api/#api-playground). - Explore [community projects built on D1](/d1/reference/community-projects/). diff --git a/src/content/docs/d1/sql-api/sql-statements.mdx b/src/content/docs/d1/sql-api/sql-statements.mdx index 8a16ad7a97f..1cb6cdc3b8b 100644 --- a/src/content/docs/d1/sql-api/sql-statements.mdx +++ b/src/content/docs/d1/sql-api/sql-statements.mdx @@ -9,7 +9,7 @@ import { Details, Render } from "~/components"; D1 is compatible with most SQLite's SQL convention since it leverages SQLite's query engine. D1 supports a number of database-level statements that allow you to list tables, indexes, and inspect the schema for a given table or index. -You can execute any of these statements via the D1 console in the Cloudflare dashboard, [`wrangler d1 execute`](/workers/wrangler/commands/d1/#d1), or with the [D1 Worker Bindings API](/d1/worker-api/d1-database). +You can execute any of these statements via the D1 console in the Cloudflare dashboard, [`wrangler d1 execute`](/workers/wrangler/commands/d1/#d1-execute), or with the [D1 Worker Bindings API](/d1/worker-api/d1-database). ## Supported SQLite extensions diff --git a/src/content/docs/kv/index.mdx b/src/content/docs/kv/index.mdx index e0dbd89af52..8f1b2cef18a 100644 --- a/src/content/docs/kv/index.mdx +++ b/src/content/docs/kv/index.mdx @@ -159,7 +159,7 @@ See the full Workers KV [REST API and SDK reference](/api/resources/kv/) for det -The Workers command-line interface, Wrangler, allows you to [create](/workers/wrangler/commands/general/#init), [test](/workers/wrangler/commands/general/#dev), and [deploy](/workers/wrangler/commands/pages/#publish) your Workers projects. +The Workers command-line interface, Wrangler, allows you to [create](/workers/wrangler/commands/general/#init), [test](/workers/wrangler/commands/general/#dev), and [deploy](/workers/wrangler/commands/pages/#pages-deploy) your Workers projects. diff --git a/src/content/docs/pages/functions/bindings.mdx b/src/content/docs/pages/functions/bindings.mdx index 0e064fc991d..46a8d660c2b 100644 --- a/src/content/docs/pages/functions/bindings.mdx +++ b/src/content/docs/pages/functions/bindings.mdx @@ -66,7 +66,7 @@ export const onRequest: PagesFunction = async (context) => { You can interact with your KV namespace bindings locally in one of two ways: -- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1). +- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev). - Pass arguments to `wrangler pages dev` directly. To interact with your KV namespace binding locally by passing arguments to the Wrangler CLI, add `-k ` or `--kv=` to the `wrangler pages dev` command. For example, if your KV namespace is bound your Function via the `TODO_LIST` binding, access the KV namespace in local development by running: @@ -132,7 +132,7 @@ export const onRequestGet: PagesFunction = async (context) => { You can interact with your Durable Object bindings locally in one of two ways: -- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1). +- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev). - Pass arguments to `wrangler pages dev` directly. While developing locally, to interact with a Durable Object namespace, run `wrangler dev` in the directory of the Worker exporting the Durable Object. In another terminal, run `wrangler pages dev` in the directory of your Pages project. @@ -196,7 +196,7 @@ export const onRequest: PagesFunction = async (context) => { You can interact with your R2 bucket bindings locally in one of two ways: -- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1). +- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev). - Pass arguments to `wrangler pages dev` directly. :::note @@ -268,7 +268,7 @@ export const onRequest: PagesFunction = async (context) => { You can interact with your D1 database bindings locally in one of two ways: -- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1). +- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev). - Pass arguments to `wrangler pages dev` directly. To interact with a D1 database via the Wrangler CLI while [developing locally](/d1/best-practices/local-development/#develop-locally-with-pages), add `--d1 =` to the `wrangler pages dev` command. @@ -493,7 +493,7 @@ export const onRequest: PagesFunction = async (context) => { You can interact with your Workers AI bindings locally in one of two ways: -- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1). +- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev). - Pass arguments to `wrangler pages dev` directly. To interact with a Workers AI binding via the Wrangler CLI while developing locally, run: @@ -549,7 +549,7 @@ export const onRequest: PagesFunction = async (context) => { You can interact with your Service bindings locally in one of two ways: -- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1). +- Configure your Pages project's Wrangler file and run [`npx wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev). - Pass arguments to `wrangler pages dev` directly. To interact with a [Service binding](/workers/runtime-apis/bindings/service-bindings/) while developing locally, run the Worker you want to bind to via `wrangler dev` and in parallel, run `wrangler pages dev` with `--service =` where `SCRIPT_NAME` indicates the name of the Worker. For example, if your Worker is called `my-worker`, connect with this Worker by running it via `npx wrangler dev` (in the Worker's directory) alongside `npx wrangler pages dev --service MY_SERVICE=my-worker` (in the Pages' directory). Interact with this binding by using `context.env` (for example, `context.env.MY_SERVICE`). @@ -715,7 +715,7 @@ export const onRequest: PagesFunction = async (context) => { ### Interact with your Hyperdrive binding locally -To interact with your Hyperdrive binding locally, you must provide a local connection string to your database that your Pages project will connect to directly. You can set an environment variable `CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_` with the connection string of the database, or use the Wrangler file to configure your Hyperdrive binding with a `localConnectionString` as specified in [Hyperdrive documentation for local development](/hyperdrive/configuration/local-development/). Then, run [`npx wrangler pages dev `](/workers/wrangler/commands/pages/#dev-1). +To interact with your Hyperdrive binding locally, you must provide a local connection string to your database that your Pages project will connect to directly. You can set an environment variable `CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_` with the connection string of the database, or use the Wrangler file to configure your Hyperdrive binding with a `localConnectionString` as specified in [Hyperdrive documentation for local development](/hyperdrive/configuration/local-development/). Then, run [`npx wrangler pages dev `](/workers/wrangler/commands/pages/#pages-dev). ## Analytics Engine @@ -830,7 +830,7 @@ export const onRequest: PagesFunction = async (context) => { You can interact with your environment variables locally in one of two ways: - Configure your Pages project's Wrangler file and running `npx wrangler pages dev`. -- Pass arguments to [`wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1) directly. +- Pass arguments to [`wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev) directly. To interact with your environment variables locally via the Wrangler CLI, add `--binding==` to the `wrangler pages dev` command: diff --git a/src/content/docs/pages/functions/debugging-and-logging.mdx b/src/content/docs/pages/functions/debugging-and-logging.mdx index b54c949cb70..7cfed946e72 100644 --- a/src/content/docs/pages/functions/debugging-and-logging.mdx +++ b/src/content/docs/pages/functions/debugging-and-logging.mdx @@ -7,7 +7,7 @@ sidebar: import { DashButton } from "~/components"; -Access your Functions logs by using the Cloudflare dashboard or the [Wrangler CLI](/workers/wrangler/commands/pages/#deployment-tail). +Access your Functions logs by using the Cloudflare dashboard or the [Wrangler CLI](/workers/wrangler/commands/pages/#pages-deployment-tail). Logs are a powerful debugging tool that can help you test and monitor the behavior of your Pages Functions once they have been deployed. Logs are available for every deployment of your Pages project. @@ -85,7 +85,7 @@ The output of each `wrangler pages deployment tail` log is a structured JSON obj } ``` -`wrangler pages deployment tail` allows you to customize a logging session to better suit your needs. Refer to the [`wrangler pages deployment tail` documentation](/workers/wrangler/commands/pages/#deployment-tail) for available configuration options. +`wrangler pages deployment tail` allows you to customize a logging session to better suit your needs. Refer to the [`wrangler pages deployment tail` documentation](/workers/wrangler/commands/pages/#pages-deployment-tail) for available configuration options. ## View logs in the Cloudflare Dashboard diff --git a/src/content/docs/pages/functions/get-started.mdx b/src/content/docs/pages/functions/get-started.mdx index 33a2c69d8b0..ad76c2d4991 100644 --- a/src/content/docs/pages/functions/get-started.mdx +++ b/src/content/docs/pages/functions/get-started.mdx @@ -44,7 +44,7 @@ Refer to [Routing](/pages/functions/routing/) for more information on route cust [Workers runtime features](/workers/runtime-apis/) are configurable on Pages Functions, including [compatibility with a subset of Node.js APIs](/workers/runtime-apis/nodejs) and the ability to set a [compatibility date or compatibility flag](/workers/configuration/compatibility-dates/). -Set these configurations by passing an argument to your [Wrangler](/workers/wrangler/commands/pages/#dev-1) command or by setting them in the dashboard. To set Pages compatibility flags in the Cloudflare dashboard: +Set these configurations by passing an argument to your [Wrangler](/workers/wrangler/commands/pages/#pages-dev) command or by setting them in the dashboard. To set Pages compatibility flags in the Cloudflare dashboard: 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account. 2. Select **Workers & Pages** and select your Pages project. diff --git a/src/content/docs/pages/functions/local-development.mdx b/src/content/docs/pages/functions/local-development.mdx index 3fa1726c44c..7af3482afcc 100644 --- a/src/content/docs/pages/functions/local-development.mdx +++ b/src/content/docs/pages/functions/local-development.mdx @@ -25,13 +25,13 @@ This will then start serving your Pages project. You can press `b` to open the b :::note -If you have a [Wrangler configuration file](/pages/functions/wrangler-configuration/) file configured for your Pages project, you can run [`wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1) without specifying a directory. +If you have a [Wrangler configuration file](/pages/functions/wrangler-configuration/) file configured for your Pages project, you can run [`wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev) without specifying a directory. ::: ### HTTPS support -To serve your local development server over HTTPS with a self-signed certificate, you can [set `local_protocol` via the [Wrangler configuration file](/pages/functions/wrangler-configuration/#local-development-settings) or you can pass the `--local-protocol=https` argument to [`wrangler pages dev`](/workers/wrangler/commands/pages/#dev-1): +To serve your local development server over HTTPS with a self-signed certificate, you can [set `local_protocol` via the [Wrangler configuration file](/pages/functions/wrangler-configuration/#local-development-settings) or you can pass the `--local-protocol=https` argument to [`wrangler pages dev`](/workers/wrangler/commands/pages/#pages-dev): ```sh npx wrangler pages dev --local-protocol=https diff --git a/src/content/docs/pages/functions/source-maps.mdx b/src/content/docs/pages/functions/source-maps.mdx index d7c6d483f6a..584a683212c 100644 --- a/src/content/docs/pages/functions/source-maps.mdx +++ b/src/content/docs/pages/functions/source-maps.mdx @@ -17,7 +17,7 @@ Support for uploading source maps for Pages is available now in open beta. Minim ## Source Maps -To enable source maps, provide the `--upload-source-maps` flag to [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy-1) or add the following to your Pages application's [Wrangler configuration file](/pages/functions/wrangler-configuration/) if you are using the Pages build environment: +To enable source maps, provide the `--upload-source-maps` flag to [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy) or add the following to your Pages application's [Wrangler configuration file](/pages/functions/wrangler-configuration/) if you are using the Pages build environment: @@ -29,7 +29,7 @@ To enable source maps, provide the `--upload-source-maps` flag to [`wrangler pag -When uploading source maps is enabled, Wrangler will automatically generate and upload source map files when you run [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy-1). +When uploading source maps is enabled, Wrangler will automatically generate and upload source map files when you run [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy). ## Stack traces diff --git a/src/content/docs/pages/get-started/direct-upload.mdx b/src/content/docs/pages/get-started/direct-upload.mdx index e9e2b30a8d7..44e0133fe77 100644 --- a/src/content/docs/pages/get-started/direct-upload.mdx +++ b/src/content/docs/pages/get-started/direct-upload.mdx @@ -51,7 +51,7 @@ To begin, install [`npm`](https://docs.npmjs.com/getting-started). Then [install #### Create your project -Log in to Wrangler with the [`wrangler login` command](/workers/wrangler/commands/general/#login). Then run the [`pages project create` command](/workers/wrangler/commands/pages/#project-create): +Log in to Wrangler with the [`wrangler login` command](/workers/wrangler/commands/general/#login). Then run the [`pages project create` command](/workers/wrangler/commands/pages/#pages-project-create): ```sh npx wrangler pages project create @@ -63,7 +63,7 @@ Subsequent deployments will reuse both of these values (saved in your `node_modu #### Deploy your assets -From here, you have created an empty project and can now deploy your assets for your first deployment and for all subsequent deployments in your production environment. To do this, run the [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy-1) command: +From here, you have created an empty project and can now deploy your assets for your first deployment and for all subsequent deployments in your production environment. To do this, run the [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy) command: ```sh npx wrangler pages deploy @@ -97,13 +97,13 @@ If you would like to streamline the project creation and asset deployment steps, #### Other useful commands -If you would like to use Wrangler to obtain a list of all available projects for Direct Upload, use [`pages project list`](/workers/wrangler/commands/pages/#project-list): +If you would like to use Wrangler to obtain a list of all available projects for Direct Upload, use [`pages project list`](/workers/wrangler/commands/pages/#pages-project-list): ```sh npx wrangler pages project list ``` -If you would like to use Wrangler to obtain a list of all unique preview URLs for a particular project, use [`pages deployment list`](/workers/wrangler/commands/pages/#deployment-list): +If you would like to use Wrangler to obtain a list of all unique preview URLs for a particular project, use [`pages deployment list`](/workers/wrangler/commands/pages/#pages-deployment-list): ```sh npx wrangler pages deployment list diff --git a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx index d04e963bc10..eae45e2e7a6 100644 --- a/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx +++ b/src/content/docs/pages/how-to/use-direct-upload-with-continuous-integration.mdx @@ -156,7 +156,7 @@ Wrangler requires a Node version of at least `16.17.0`. You must upgrade your No ::: -You can modify the Wrangler command with any [`wrangler pages deploy` options](/workers/wrangler/commands/general/#deploy-1). +You can modify the Wrangler command with any [`wrangler pages deploy` options](/workers/wrangler/commands/general/#deploy). After all the specified steps, define a `workflow` at the end of your file. You can learn more about creating a custom process with CircleCI from the [official documentation](https://circleci.com/docs/2.0/concepts/). @@ -195,4 +195,4 @@ env: This will set the Node.js version to 18. You have also set branches you want your continuous integration to run on. Finally, input your `PROJECT NAME` in the script section and your CI process should work as expected. -You can also modify the Wrangler command with any [`wrangler pages deploy` options](/workers/wrangler/commands/general/#deploy-1). +You can also modify the Wrangler command with any [`wrangler pages deploy` options](/workers/wrangler/commands/general/#deploy). diff --git a/src/content/docs/pages/tutorials/build-an-api-with-pages-functions.mdx b/src/content/docs/pages/tutorials/build-an-api-with-pages-functions.mdx index 3b2fa7c5cd1..738d2376742 100644 --- a/src/content/docs/pages/tutorials/build-an-api-with-pages-functions.mdx +++ b/src/content/docs/pages/tutorials/build-an-api-with-pages-functions.mdx @@ -219,7 +219,7 @@ After you have configured your Pages application and Pages Function, deploy your ### Deploy with Wrangler -In your `blog-frontend` directory, run [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy-1) to deploy your project to the Cloudflare dashboard. +In your `blog-frontend` directory, run [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy) to deploy your project to the Cloudflare dashboard. ```sh wrangler pages deploy blog-frontend diff --git a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips.mdx b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips.mdx index dc951becccc..bc825988ae0 100644 --- a/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips.mdx +++ b/src/content/docs/smart-shield/configuration/dedicated-egress-ips/how-it-works/egress-ips.mdx @@ -10,7 +10,7 @@ head: import { Render } from "~/components"; -When you use Cloudflare [as a reverse proxy](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy), [Cloudflare's global network](https://www.cloudflare.com/network/) sits between client requests and your origin servers. +When you use Cloudflare [as a reverse proxy](/fundamentals/concepts/how-cloudflare-works/#cloudflare-as-a-reverse-proxy), [Cloudflare's global network](https://www.cloudflare.com/network/) sits between client requests and your origin servers. ```mermaid flowchart LR diff --git a/src/content/docs/workers/ci-cd/builds/build-branches.mdx b/src/content/docs/workers/ci-cd/builds/build-branches.mdx index e342f68aee2..99d32b8995a 100644 --- a/src/content/docs/workers/ci-cd/builds/build-branches.mdx +++ b/src/content/docs/workers/ci-cd/builds/build-branches.mdx @@ -15,7 +15,7 @@ To change the production branch of your project: 1. In **Overview**, select your Workers project. 2. Go to **Settings** > **Build** > **Branch control**. Workers will default to the default branch of your git repository, but this can be changed in the dropdown. -Every push event made to this branch will trigger a build and execute the [build command](/workers/ci-cd/builds/configuration/#build-command), followed by the [deploy command](/workers/ci-cd/builds/configuration/#deploy-command). +Every push event made to this branch will trigger a build and execute the [build command](/workers/ci-cd/builds/configuration/#deploy-command), followed by the [deploy command](/workers/ci-cd/builds/configuration/#deploy-command). ## Configure non-production branch builds @@ -24,4 +24,4 @@ To enable or disable non-production branch builds: 1. In **Overview**, select your Workers project. 2. Go to **Settings** > **Build** > **Branch control**. The checkbox **Builds for non-production branches** allows you to enable or disable builds for non-production branches. -When enabled, every push event made to a non-production branch will trigger a build and execute the [build command](/workers/ci-cd/builds/configuration/#build-command), followed by the [non-production branch deploy command](/workers/ci-cd/builds/configuration/#non-production-branch-deploy-command). +When enabled, every push event made to a non-production branch will trigger a build and execute the [build command](/workers/ci-cd/builds/configuration/#deploy-command), followed by the [non-production branch deploy command](/workers/ci-cd/builds/configuration/#non-production-branch-deploy-command). diff --git a/src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx b/src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx index d60dd7f0cee..b2d0d9857b1 100644 --- a/src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx +++ b/src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx @@ -168,7 +168,7 @@ Then, update your configuration file's `main` field to point to the location of ##### Pages Functions with a `functions/` folder -If you use **Pages Functions with a [folder of `functions/`](/pages/functions/)**, you must first compile these functions into a single Worker script with the [`wrangler pages functions build`](/workers/wrangler/commands/pages/#functions-build) command. +If you use **Pages Functions with a [folder of `functions/`](/pages/functions/)**, you must first compile these functions into a single Worker script with the [`wrangler pages functions build`](/workers/wrangler/commands/pages/#pages-functions-build) command. - The migration directory containing the migration files. By default, `wrangler d1 migrations create` creates a folder named `migrations`. You can use `migrations_dir` to specify a different folder containing the migration files (for example, if you have a mono-repo setup, and want to use a single D1 instance across your apps/packages). - - For more information, refer to [D1 Wrangler `migrations` commands](/workers/wrangler/commands/d1/#migrations-create) and [D1 migrations](/d1/reference/migrations/). + - For more information, refer to [D1 Wrangler `migrations` commands](/workers/wrangler/commands/d1/#d1-migrations-create) and [D1 migrations](/d1/reference/migrations/). :::note diff --git a/src/content/docs/workers/wrangler/deprecations.mdx b/src/content/docs/workers/wrangler/deprecations.mdx index 1dec24ebb06..2153f0008de 100644 --- a/src/content/docs/workers/wrangler/deprecations.mdx +++ b/src/content/docs/workers/wrangler/deprecations.mdx @@ -41,7 +41,7 @@ Use [`npx wrangler deploy`](/workers/wrangler/commands/general/#deploy) to deplo The `wrangler pages publish` command is deprecated, but still active in v3. `wrangler pages publish` will be fully removed in v4. -Use [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy-1) to deploy Pages. +Use [`wrangler pages deploy`](/workers/wrangler/commands/general/#deploy) to deploy Pages. #### `version` diff --git a/src/content/partials/hyperdrive/planetscale-placement-partial.mdx b/src/content/partials/hyperdrive/planetscale-placement-partial.mdx index c3af3f51079..ef24f19b34a 100644 --- a/src/content/partials/hyperdrive/planetscale-placement-partial.mdx +++ b/src/content/partials/hyperdrive/planetscale-placement-partial.mdx @@ -4,7 +4,7 @@ :::note -To reduce latency, use a [Placement Hint](/workers/configuration/placement/#use-placement-hints) to run your Worker close to your PlanetScale database. This is especially useful when a single request makes multiple queries. +To reduce latency, use a [Placement Hint](/workers/configuration/placement/#configure-explicit-placement-hints) to run your Worker close to your PlanetScale database. This is especially useful when a single request makes multiple queries. ```jsonc title="wrangler.jsonc" { diff --git a/src/content/release-notes/hyperdrive.yaml b/src/content/release-notes/hyperdrive.yaml index de15ddd87b6..fecc2da1fea 100644 --- a/src/content/release-notes/hyperdrive.yaml +++ b/src/content/release-notes/hyperdrive.yaml @@ -51,7 +51,7 @@ entries: description: |- Hyperdrive query caching now happens in all locations where Hyperdrive can be accessed. When making a query in a location that has cached the query result, your latency may be decreased by up to 90%. - Refer to [documentation on how Hyperdrive caches query results](/hyperdrive/concepts/how-hyperdrive-works/#query-caching). + Refer to [documentation on how Hyperdrive caches query results](/hyperdrive/concepts/how-hyperdrive-works/#3-query-caching). - publish_date: "2024-11-19" title: Hyperdrive now supports clear-text password authentication description: |- diff --git a/src/content/warp-releases/linux/beta/2025.10.118.1.yaml b/src/content/warp-releases/linux/beta/2025.10.118.1.yaml index 34635b95c02..5bbd73875fa 100644 --- a/src/content/warp-releases/linux/beta/2025.10.118.1.yaml +++ b/src/content/warp-releases/linux/beta/2025.10.118.1.yaml @@ -4,7 +4,7 @@ releaseNotes: |- **Changes and improvements** - The [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) feature has been fixed for devices running WARP client version 2025.4.929.0 and newer. Previously, these devices could experience failures with Local Domain Fallback unless a fallback server was explicitly configured. This configuration is no longer a requirement for the feature to function correctly. - Linux [disk encryption posture check](/cloudflare-one/reusable-components/posture-checks/warp-client-checks/disk-encryption/) now supports non-filesystem encryption types like `dm-crypt`. - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. - Fixed an issue where the GUI becomes unresponsive when the **Re-Authenticate in browser** button is clicked. version: 2025.10.118.1 releaseDate: 2025-12-08T19:35:40.098Z diff --git a/src/content/warp-releases/linux/beta/2025.7.106.1.yaml b/src/content/warp-releases/linux/beta/2025.7.106.1.yaml index 16fd654676f..f2470a0ecd4 100644 --- a/src/content/warp-releases/linux/beta/2025.7.106.1.yaml +++ b/src/content/warp-releases/linux/beta/2025.7.106.1.yaml @@ -1,8 +1,8 @@ releaseNotes: |- - This release contains minor fixes and improvements including enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. + This release contains minor fixes and improvements including enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. **Changes and improvements** - - Enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. + - Enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. - The [MASQUE protocol](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#device-tunnel-protocol) is now the default protocol for all new WARP device profiles. - Improvement to limit idle connections in DoH mode to avoid unnecessary resource usage that can lead to DoH requests not resolving. - Improvements to maintain Global WARP Override settings when switching between organization configurations. diff --git a/src/content/warp-releases/linux/ga/2025.10.186.0.yaml b/src/content/warp-releases/linux/ga/2025.10.186.0.yaml index db90a214ce3..f45907e4ff2 100644 --- a/src/content/warp-releases/linux/ga/2025.10.186.0.yaml +++ b/src/content/warp-releases/linux/ga/2025.10.186.0.yaml @@ -6,7 +6,7 @@ releaseNotes: |- **Changes and improvements** - The [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) feature has been fixed for devices running WARP client version 2025.4.929.0 and newer. Previously, these devices could experience failures with Local Domain Fallback unless a fallback server was explicitly configured. This configuration is no longer a requirement for the feature to function correctly. - Linux [disk encryption posture check](/cloudflare-one/reusable-components/posture-checks/warp-client-checks/disk-encryption/) now supports non-filesystem encryption types like `dm-crypt`. - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. - Fixed an issue where the GUI becomes unresponsive when the **Re-Authenticate in browser** button is clicked. - Added a new feature to manage WARP client connectivity for all devices using an [external signal](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/external-disconnect/). This feature allows administrators to send a global signal from an on-premises HTTPS endpoint that force disconnects or reconnects all WARP clients in an account based on configuration set on the endpoint. version: 2025.10.186.0 diff --git a/src/content/warp-releases/linux/ga/2025.7.176.0.yaml b/src/content/warp-releases/linux/ga/2025.7.176.0.yaml index 3f334d7a774..5403b696c42 100644 --- a/src/content/warp-releases/linux/ga/2025.7.176.0.yaml +++ b/src/content/warp-releases/linux/ga/2025.7.176.0.yaml @@ -3,8 +3,8 @@ releaseNotes: |- **Changes and improvements** - MASQUE is now the default [tunnel protocol](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#device-tunnel-protocol) for all new WARP device profiles. - - Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#gateway-with-doh) to avoid unnecessary resource usage that can lead to DoH requests not resolving. - - Improvements to maintain [Global WARP override](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#disconnect-warp-on-all-devices) settings when [switching between organizations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-warp). + - Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode) to avoid unnecessary resource usage that can lead to DoH requests not resolving. + - Improvements to maintain [Global WARP override](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#disconnect-warp-on-all-devices) settings when [switching between organizations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-the-cloudflare-one-client). - Improvements to maintain client connectivity during network changes. **Known issues** diff --git a/src/content/warp-releases/linux/ga/2025.8.779.0.yaml b/src/content/warp-releases/linux/ga/2025.8.779.0.yaml index 2924fe31169..afc7b917b26 100644 --- a/src/content/warp-releases/linux/ga/2025.8.779.0.yaml +++ b/src/content/warp-releases/linux/ga/2025.8.779.0.yaml @@ -3,9 +3,9 @@ releaseNotes: |- **Changes and improvements** - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases. - - The MASQUE protocol is now the only protocol that can use [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode). If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity. + - The MASQUE protocol is now the only protocol that can use [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode). If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity. **Known issues** diff --git a/src/content/warp-releases/macos/beta/2025.10.118.1.yaml b/src/content/warp-releases/macos/beta/2025.10.118.1.yaml index 4b910048691..61d168ab557 100644 --- a/src/content/warp-releases/macos/beta/2025.10.118.1.yaml +++ b/src/content/warp-releases/macos/beta/2025.10.118.1.yaml @@ -3,7 +3,7 @@ releaseNotes: |- **Changes and improvements** - The [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) feature has been fixed for devices running WARP client version 2025.4.929.0 and newer. Previously, these devices could experience failures with Local Domain Fallback unless a fallback server was explicitly configured. This configuration is no longer a requirement for the feature to function correctly. - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. version: 2025.10.118.1 releaseDate: 2025-12-09T23:02:28.072Z packageURL: https://downloads.cloudflareclient.com/v1/download/macos/version/2025.10.118.1 diff --git a/src/content/warp-releases/macos/beta/2025.7.106.1.yaml b/src/content/warp-releases/macos/beta/2025.7.106.1.yaml index 8da7c7d450e..ad73668380c 100644 --- a/src/content/warp-releases/macos/beta/2025.7.106.1.yaml +++ b/src/content/warp-releases/macos/beta/2025.7.106.1.yaml @@ -1,8 +1,8 @@ releaseNotes: |- - This release contains minor fixes and improvements including enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. + This release contains minor fixes and improvements including enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. **Changes and improvements** - - Enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. + - Enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. - Fixed a bug preventing the `warp-diag captive-portal` command from running successfully due to the client not parsing SSID on macOS. - Improvements to maintain Global WARP Override settings when switching between organization configurations. - The [MASQUE protocol](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#device-tunnel-protocol) is now the default protocol for all new WARP device profiles. diff --git a/src/content/warp-releases/macos/ga/2025.10.186.0.yaml b/src/content/warp-releases/macos/ga/2025.10.186.0.yaml index 7cffe46f71d..44ebcfc012b 100644 --- a/src/content/warp-releases/macos/ga/2025.10.186.0.yaml +++ b/src/content/warp-releases/macos/ga/2025.10.186.0.yaml @@ -3,7 +3,7 @@ releaseNotes: |- **Changes and improvements** - The [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) feature has been fixed for devices running WARP client version 2025.4.929.0 and newer. Previously, these devices could experience failures with Local Domain Fallback unless a fallback server was explicitly configured. This configuration is no longer a requirement for the feature to function correctly. - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. - Added a new feature to manage WARP client connectivity for all devices using an [external signal](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/external-disconnect/). This feature allows administrators to send a global signal from an on-premises HTTPS endpoint that force disconnects or reconnects all WARP clients in an account based on configuration set on the endpoint. version: 2025.10.186.0 releaseDate: 2026-01-13T15:48:17.930Z diff --git a/src/content/warp-releases/macos/ga/2025.7.176.0.yaml b/src/content/warp-releases/macos/ga/2025.7.176.0.yaml index 4c2c8e4fdbc..42703e8b9a2 100644 --- a/src/content/warp-releases/macos/ga/2025.7.176.0.yaml +++ b/src/content/warp-releases/macos/ga/2025.7.176.0.yaml @@ -3,9 +3,9 @@ releaseNotes: |- **Changes and improvements** - Fixed a bug preventing the `warp-diag captive-portal` command from running successfully due to the client not parsing SSID on macOS. - - Improvements to maintain [Global WARP override](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#disconnect-warp-on-all-devices) settings when [switching between organizations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-warp). + - Improvements to maintain [Global WARP override](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#disconnect-warp-on-all-devices) settings when [switching between organizations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-the-cloudflare-one-client). - MASQUE is now the default [tunnel protocol](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#device-tunnel-protocol) for all new WARP device profiles. - - Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#gateway-with-doh) to avoid unnecessary resource usage that can lead to DoH requests not resolving. + - Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode) to avoid unnecessary resource usage that can lead to DoH requests not resolving. - Improvements to maintain client connectivity during network changes. - The WARP client now supports macOS Tahoe (version 26.0). diff --git a/src/content/warp-releases/macos/ga/2025.8.779.0.yaml b/src/content/warp-releases/macos/ga/2025.8.779.0.yaml index 641a1c09455..944a0981ec2 100644 --- a/src/content/warp-releases/macos/ga/2025.8.779.0.yaml +++ b/src/content/warp-releases/macos/ga/2025.8.779.0.yaml @@ -3,9 +3,9 @@ releaseNotes: |- **Changes and improvements** - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases. - - The MASQUE protocol is now the only protocol that can use [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode). If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity. + - The MASQUE protocol is now the only protocol that can use [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode). If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity. **Known issues** diff --git a/src/content/warp-releases/windows/beta/2025.10.118.1.yaml b/src/content/warp-releases/windows/beta/2025.10.118.1.yaml index 4d4baf7f62b..a89fb6ce94a 100644 --- a/src/content/warp-releases/windows/beta/2025.10.118.1.yaml +++ b/src/content/warp-releases/windows/beta/2025.10.118.1.yaml @@ -3,7 +3,7 @@ releaseNotes: |- **Changes and improvements** - The [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) feature has been fixed for devices running WARP client version 2025.4.929.0 and newer. Previously, these devices could experience failures with Local Domain Fallback unless a fallback server was explicitly configured. This configuration is no longer a requirement for the feature to function correctly. - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. - Fixed an issue where sending large messages to the WARP daemon by Inter-Process Communication (IPC) could cause WARP to crash and result in service interruptions. **Known issues** diff --git a/src/content/warp-releases/windows/beta/2025.2.460.1.yaml b/src/content/warp-releases/windows/beta/2025.2.460.1.yaml index 8dda67debcd..d5de76bf33d 100644 --- a/src/content/warp-releases/windows/beta/2025.2.460.1.yaml +++ b/src/content/warp-releases/windows/beta/2025.2.460.1.yaml @@ -11,7 +11,7 @@ releaseNotes: >- - Improved error messages shown in the app. - Added the ability to control if the WARP interface IPs are [registered with - DNS servers](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#warp-interface-ip-dns-registration) or not. + DNS servers](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#client-interface-ip-dns-registration) or not. - Removed DNS logs view from the Windows client GUI. DNS logs can be viewed as part of `warp-diag` or by viewing the log file on the user's local directory. diff --git a/src/content/warp-releases/windows/beta/2025.7.106.1.yaml b/src/content/warp-releases/windows/beta/2025.7.106.1.yaml index 5493427f525..d6aa2f13f83 100644 --- a/src/content/warp-releases/windows/beta/2025.7.106.1.yaml +++ b/src/content/warp-releases/windows/beta/2025.7.106.1.yaml @@ -1,8 +1,8 @@ releaseNotes: |- - This release contains minor fixes and improvements including enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. + This release contains minor fixes and improvements including enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. **Changes and improvements** - - Enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. + - Enhancements to [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) for even faster resolution. The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new [WARP mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/) or all devices matching the profile will lose connectivity. - Improvement to keep TCP connections up the first time WARP connects on devices so that remote desktop sessions (such as RDP or SSH) continue to work. - Improvements to maintain Global WARP Override settings when switching between organization configurations. - The [MASQUE protocol](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#device-tunnel-protocol) is now the default protocol for all new WARP device profiles. diff --git a/src/content/warp-releases/windows/ga/2025.10.186.0.yaml b/src/content/warp-releases/windows/ga/2025.10.186.0.yaml index a8d43a3c380..6ed843d9761 100644 --- a/src/content/warp-releases/windows/ga/2025.10.186.0.yaml +++ b/src/content/warp-releases/windows/ga/2025.10.186.0.yaml @@ -5,7 +5,7 @@ releaseNotes: |- - Added a new feature to manage WARP client connectivity for all devices using an [external signal](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/external-disconnect/). This feature allows administrators to send a global signal from an on-premises HTTPS endpoint that force disconnects or reconnects all WARP clients in an account based on configuration set on the endpoint. - Fixed an issue that caused occasional audio degradation and increased CPU usage on Windows by optimizing route configurations for large [domain-based split tunnel rules](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/#domain-based-split-tunnels). - The [Local Domain Fallback](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/local-domains/) feature has been fixed for devices running WARP client version 2025.4.929.0 and newer. Previously, these devices could experience failures with Local Domain Fallback unless a fallback server was explicitly configured. This configuration is no longer a requirement for the feature to function correctly. - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) now supports transparent HTTP proxying in addition to CONNECT-based proxying. - Fixed an issue where sending large messages to the daemon by Inter-Process Communication (IPC) could cause the daemon to fail and result in service interruptions. - Added support for a new WARP client device posture check for [Antivirus](/cloudflare-one/reusable-components/posture-checks/warp-client-checks/antivirus/). The check confirms the presence of an antivirus program on a Windows device with the option to check if the antivirus is up to date. diff --git a/src/content/warp-releases/windows/ga/2025.2.600.0.yaml b/src/content/warp-releases/windows/ga/2025.2.600.0.yaml index c0fe2ba273d..97bfb741d81 100644 --- a/src/content/warp-releases/windows/ga/2025.2.600.0.yaml +++ b/src/content/warp-releases/windows/ga/2025.2.600.0.yaml @@ -8,7 +8,7 @@ releaseNotes: >- - Improved error messages shown in the app. - - Added the ability to control if the WARP interface IPs are [registered with DNS servers](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#warp-interface-ip-dns-registration) or not. + - Added the ability to control if the WARP interface IPs are [registered with DNS servers](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#client-interface-ip-dns-registration) or not. - Removed DNS logs view from the Windows client GUI. DNS logs can be viewed as part of `warp-diag` or by viewing the log file on the user's local directory. diff --git a/src/content/warp-releases/windows/ga/2025.7.176.0.yaml b/src/content/warp-releases/windows/ga/2025.7.176.0.yaml index 3935daea003..70aa1d55822 100644 --- a/src/content/warp-releases/windows/ga/2025.7.176.0.yaml +++ b/src/content/warp-releases/windows/ga/2025.7.176.0.yaml @@ -3,9 +3,9 @@ releaseNotes: |- **Changes and improvements** - MASQUE is now the default [tunnel protocol](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#device-tunnel-protocol) for all new WARP device profiles. - - Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#gateway-with-doh) to avoid unnecessary resource usage that can lead to DoH requests not resolving. + - Improvement to limit idle connections in [Gateway with DoH mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#dns-only-mode) to avoid unnecessary resource usage that can lead to DoH requests not resolving. - Improvement to maintain TCP connections to reduce interruptions in long-lived connections such as RDP or SSH. - - Improvements to maintain [Global WARP override](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#disconnect-warp-on-all-devices) settings when [switching between organizations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-warp). + - Improvements to maintain [Global WARP override](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/settings/#disconnect-warp-on-all-devices) settings when [switching between organizations](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/switch-organizations/#switch-organizations-in-the-cloudflare-one-client). - Improvements to maintain client connectivity during network changes. **Known issues** diff --git a/src/content/warp-releases/windows/ga/2025.8.779.0.yaml b/src/content/warp-releases/windows/ga/2025.8.779.0.yaml index 13df055a6e9..076ac45df8f 100644 --- a/src/content/warp-releases/windows/ga/2025.8.779.0.yaml +++ b/src/content/warp-releases/windows/ga/2025.8.779.0.yaml @@ -3,9 +3,9 @@ releaseNotes: |- **Changes and improvements** - - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode) has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases. + - [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode) has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases. - - The MASQUE protocol is now the only protocol that can use [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#proxy-mode). If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity. + - The MASQUE protocol is now the only protocol that can use [Proxy mode](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/modes/#local-proxy-mode). If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity. **Known issues** diff --git a/src/content/warp-releases/windows/ga/2025.9.558.0.yaml b/src/content/warp-releases/windows/ga/2025.9.558.0.yaml index c02bfa349b0..2c05ffc30fc 100644 --- a/src/content/warp-releases/windows/ga/2025.9.558.0.yaml +++ b/src/content/warp-releases/windows/ga/2025.9.558.0.yaml @@ -7,7 +7,7 @@ releaseNotes: |- - Fixed an issue where deleting a registration was erroneously reported as having failed. - Path Maximum Transmission Unit Discovery (PMTUD) may now be used to discover the effective MTU of the connection. This allows the WARP client to improve connectivity optimized for each network. PMTUD is disabled by default. To enable it, refer to the [PMTUD documentation](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/mdm-deployment/path-mtu-discovery/#enable-path-mtu-discovery). - Improvements for the [OS version](/cloudflare-one/reusable-components/posture-checks/warp-client-checks/os-version/) WARP client check. Windows Updated Build Revision (UBR) numbers can now be checked by the client to ensure devices have required security patches and features installed. - - The WARP client now supports Windows 11 ARM-based machines. For information on known limitations, refer to the [Known limitations page](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/known-limitations/#warp-disconnected-on-windows-arm). + - The WARP client now supports Windows 11 ARM-based machines. For information on known limitations, refer to the [Known limitations page](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/troubleshooting/known-limitations/#cloudflare-one-client-disconnected-on-windows-arm). **Known issues** - For Windows 11 24H2 users, Microsoft has confirmed a regression that may lead to performance issues like mouse lag, audio cracking, or other slowdowns. Cloudflare recommends users experiencing these issues upgrade to a minimum [Windows 11 24H2 KB5062553](https://support.microsoft.com/en-us/topic/july-8-2025-kb5062553-os-build-26100-4652-523e69cb-051b-43c6-8376-6a76d6caeefd) or higher for resolution.