diff --git a/src/content/docs/ai-gateway/configuration/caching.mdx b/src/content/docs/ai-gateway/configuration/caching.mdx index 3874e00d8c06e2..2d9e981e4dcdef 100644 --- a/src/content/docs/ai-gateway/configuration/caching.mdx +++ b/src/content/docs/ai-gateway/configuration/caching.mdx @@ -23,7 +23,7 @@ We plan on adding semantic search for caching in the future to improve cache hit ## Default configuration - + To set the default caching configuration in the dashboard: @@ -33,7 +33,7 @@ To set the default caching configuration in the dashboard: 4. Enable **Cache Responses**. 5. Change the default caching to whatever value you prefer. - + To set the default caching configuration using the API: diff --git a/src/content/docs/ai-gateway/configuration/rate-limiting.mdx b/src/content/docs/ai-gateway/configuration/rate-limiting.mdx index fa46b60e66c31d..934ed722980ff2 100644 --- a/src/content/docs/ai-gateway/configuration/rate-limiting.mdx +++ b/src/content/docs/ai-gateway/configuration/rate-limiting.mdx @@ -20,7 +20,7 @@ To illustrate this, let us say you had a limit of ten requests per ten minutes, ## Default configuration - + To set the default rate limiting configuration in the dashboard: @@ -30,7 +30,7 @@ To set the default rate limiting configuration in the dashboard: 4. Enable **Rate-limiting**. 5. Adjust the rate, time period, and rate limiting method as desired. - + To set the default rate limiting configuration using the API: diff --git a/src/content/docs/ai-gateway/observability/analytics.mdx b/src/content/docs/ai-gateway/observability/analytics.mdx index bf5b7b9d14533b..2b1efa7a89fdeb 100644 --- a/src/content/docs/ai-gateway/observability/analytics.mdx +++ b/src/content/docs/ai-gateway/observability/analytics.mdx @@ -10,7 +10,7 @@ import { Render, TabItem, Tabs } from "~/components" ## View analytics - + diff --git a/src/content/docs/argo-smart-routing/get-started.mdx b/src/content/docs/argo-smart-routing/get-started.mdx index d8ad6a296f439b..8244736ad9266f 100644 --- a/src/content/docs/argo-smart-routing/get-started.mdx +++ b/src/content/docs/argo-smart-routing/get-started.mdx @@ -12,7 +12,7 @@ import { Render, TabItem, Tabs } from "~/components" Argo Smart Routing is a one-click solution to speed up your global traffic. - + To enable [Argo Smart Routing](https://dash.cloudflare.com/?to=/:account/:zone/traffic) in the dashboard: @@ -25,7 +25,7 @@ To enable [Argo Smart Routing](https://dash.cloudflare.com/?to=/:account/:zone/t * If you have a billing profile, confirm your billing information. - + To enable or disable Argo Smart Routing with the API, send a [`PATCH`](/api/operations/argo-smart-routing-patch-argo-smart-routing-setting) request with the `value` parameter set to your desired setting (`"on"` or `"off"`). diff --git a/src/content/docs/browser-rendering/get-started/screenshots.mdx b/src/content/docs/browser-rendering/get-started/screenshots.mdx index 67f7954609c2c0..b1737e6190ac0e 100644 --- a/src/content/docs/browser-rendering/get-started/screenshots.mdx +++ b/src/content/docs/browser-rendering/get-started/screenshots.mdx @@ -65,7 +65,7 @@ kv_namespaces = [ ## 5. Code - + Update `src/index.js` with your Worker code: ```js @@ -103,7 +103,7 @@ export default { }; ``` - + Update `src/worker.ts` with your Worker code: ```ts diff --git a/src/content/docs/browser-rendering/platform/puppeteer.mdx b/src/content/docs/browser-rendering/platform/puppeteer.mdx index d7cc3fe9027577..3e6435588b6bc2 100644 --- a/src/content/docs/browser-rendering/platform/puppeteer.mdx +++ b/src/content/docs/browser-rendering/platform/puppeteer.mdx @@ -24,7 +24,7 @@ npm install @cloudflare/puppeteer --save-dev Once the [browser binding](/browser-rendering/platform/wrangler/#bindings) is configured and the `@cloudflare/puppeteer` library is installed, Puppeteer can be used in a Worker: - + ```js import puppeteer from "@cloudflare/puppeteer"; @@ -41,7 +41,7 @@ export default { }; ``` - + ```ts import puppeteer from "@cloudflare/puppeteer"; diff --git a/src/content/docs/byoip/concepts/dynamic-advertisement/best-practices.mdx b/src/content/docs/byoip/concepts/dynamic-advertisement/best-practices.mdx index 414367f3d1e8a0..f6b5ce80da5671 100644 --- a/src/content/docs/byoip/concepts/dynamic-advertisement/best-practices.mdx +++ b/src/content/docs/byoip/concepts/dynamic-advertisement/best-practices.mdx @@ -62,14 +62,14 @@ Most dynamic advertisement operations require that you supply the Cloudflare ID ## Obtain prefix IDs - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. 2. Go to **IP Addresses** > **IP Prefixes**. 3. Find the CIDR for which you want the prefix ID, and select the arrow next to it. 4. The prefix ID is the value under **API Tag**. Select **Copy** to add the value to your clipboard. - + To obtain prefix IDs using the API, refer to the [list prefixes](/api/operations/ip-address-management-prefixes-list-prefixes) operation in the Cloudflare API. diff --git a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx index d00798fdd56bb5..bdd0bd6498d4e1 100644 --- a/src/content/docs/cache/advanced-configuration/cache-reserve.mdx +++ b/src/content/docs/cache/advanced-configuration/cache-reserve.mdx @@ -22,13 +22,13 @@ Cache Reserve is a usage-based product and [pricing](#pricing) is detailed below A paid Cache Reserve Plan is required for the enablement. - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select a domain. 2. Go to **Caching** > **Cache Reserve**. 3. Select **Enable storage sync**. - + Refer to the [Change Cache Reserve setting API](/api/operations/zone-cache-settings-change-cache-reserve-setting) for more information. @@ -195,13 +195,13 @@ You can remove all data stored in Cache Reserve through the dashboard or via API Be aware that the deletion may take up to 24 hours to complete. - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select a domain. 2. Go to **Caching** > **Cache Reserve**. 3. In **Delete Cache Reserve Data**, select **Delete Storage**. - + To delete Cache Reserve data via API use the following example requests. For more information, refer to the [API documentation](/api/operations/zone-cache-settings-start-cache-reserve-clear). diff --git a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx index b82244d2c1cd42..ac1b9648ee75f2 100644 --- a/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx +++ b/src/content/docs/cache/how-to/cache-rules/page-rules-migration.mdx @@ -21,7 +21,7 @@ Multiple matching cache rules can be combined and applied to the same request. A ## Rule 1 - + 1. Enter a rule name, for instance `bypass everything`. 2. In **When incoming requests match**, select **All incoming requests**. @@ -35,7 +35,7 @@ Multiple matching cache rules can be combined and applied to the same request. A ## Rule 2 - + 1. Enter a rule name, for instance `cache all default cacheable extensions`. 2. In **When incoming requests match**, select **Custom filter expression**. diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/create-custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/create-custom-hostnames.mdx index f6a96c812a2554..f7743c9734cd55 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/create-custom-hostnames.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/create-custom-hostnames.mdx @@ -14,13 +14,13 @@ There are several required steps before a custom hostname can become active. For To create a custom hostname: - + - + diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/remove-custom-hostnames.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/remove-custom-hostnames.mdx index 23d262629ee305..37a09a3a132ad9 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/remove-custom-hostnames.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/remove-custom-hostnames.mdx @@ -29,11 +29,11 @@ If your customer's domain is not using Cloudflare, you must remove a customer's This is especially important if your end customers are using Cloudflare because if the custom hostname changes the DNS target to point away from your SaaS zone, the custom hostname will continue to route to your service. This is a result of the [custom hostname priority logic](/ssl/reference/certificate-and-hostname-priority/#hostname-priority-cloudflare-for-saas). - + - + To delete a custom hostname and any issued certificates using the API, send a [`DELETE` request](/api/operations/custom-hostname-for-a-zone-delete-custom-hostname-\(-and-any-issued-ssl-certificates\)). diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt.mdx index 0432ad664ce0b0..484de3dc501a91 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt.mdx @@ -37,13 +37,13 @@ Once you [create a new hostname](/cloudflare-for-platforms/cloudflare-for-saas/s - + - + diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/agentless/pac-files.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/agentless/pac-files.mdx index e376345a6ae975..546e9748694355 100644 --- a/src/content/docs/cloudflare-one/connections/connect-devices/agentless/pac-files.mdx +++ b/src/content/docs/cloudflare-one/connections/connect-devices/agentless/pac-files.mdx @@ -37,7 +37,7 @@ All devices you add to the proxy endpoint will be able to access your Cloudflare - + 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Proxy Endpoints**. @@ -68,7 +68,7 @@ https://.proxy.cloudflare-gateway.com - + 1. [Create a proxy endpoint](/api/operations/zero-trust-gateway-proxy-endpoints-create-proxy-endpoint) with the following call: diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles.mdx index 2272d694b4c42f..e497158f5da533 100644 --- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles.mdx +++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles.mdx @@ -12,7 +12,7 @@ import { Render, TabItem, Tabs } from "~/components" ## Create a new profile - + 1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**. 2. In the **Profile settings** card, select **Create profile**. This will make a copy of the **Default** profile. @@ -31,7 +31,7 @@ Your profile will appear in the **Profile settings** list. You can rearrange the - + Send a `POST` request to the [Devices endpoint](/api/operations/devices-create-device-settings-policy): diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks.mdx index 0ee8bc6bc581bc..acb130600f1b4c 100644 --- a/src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks.mdx +++ b/src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks.mdx @@ -48,7 +48,7 @@ Here are a few scenarios where virtual networks may prove useful: The following example demonstrates how to add two overlapping IP routes to Cloudflare (`10.128.0.1/32` staging and `10.128.0.1/32` production). - + To route overlapping IPs over virtual networks: 1. First, create two unique virtual networks: @@ -162,7 +162,7 @@ The following example demonstrates how to add two overlapping IP routes to Cloud ## Delete a virtual network - + To delete a virtual network: 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels** and ensure that no IP routes are assigned to the virtual network you are trying to delete. If your virtual network is in use, delete the route or reassign it to a different virtual network. diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns.mdx index 15fa76694d0006..9baae76c1d545c 100644 --- a/src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns.mdx +++ b/src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns.mdx @@ -12,7 +12,7 @@ import { Render, TabItem, Tabs } from "~/components" ## Create a DNS record for the tunnel - + To create a new DNS record for your tunnel: diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb.mdx index 14892b5d661104..ada51a32c60e67 100644 --- a/src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb.mdx +++ b/src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb.mdx @@ -12,7 +12,7 @@ import { Render, TabItem, Tabs } from "~/components" ## Add a tunnel to a load balancer pool - + To create a load balancer, refer to the [Load Balancing documentation](/load-balancing/load-balancers/create-load-balancer/). The endpoint address is the subdomain of your tunnel, `.cfargotunnel.com`. diff --git a/src/content/docs/cloudflare-one/insights/logs/audit-logs.mdx b/src/content/docs/cloudflare-one/insights/logs/audit-logs.mdx index 16193e5ea2dd6d..2693ea595404fd 100644 --- a/src/content/docs/cloudflare-one/insights/logs/audit-logs.mdx +++ b/src/content/docs/cloudflare-one/insights/logs/audit-logs.mdx @@ -34,7 +34,7 @@ Authentication audit logs do not capture actions the user takes once they have a ### Identity-based authentication - + To view logs for identity-based authentication events: @@ -42,7 +42,7 @@ To view logs for identity-based authentication events: 2. Expand a row to view details such as the login method, the IP address of the user, and more. 3. If a login attempt was blocked, select **View** for information about why Access denied the user access. - + The [Access authentication logs](/api/operations/access-authentication-logs-get-access-authentication-logs) API endpoint provides a custom URL to export audit log events for your account. diff --git a/src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx b/src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx index dda6243a12250c..8b5fbc69386a21 100644 --- a/src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx +++ b/src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx @@ -40,7 +40,7 @@ Make sure you have: First, create [virtual networks](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) corresponding to your dedicated egress IPs. - + 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **WARP Client**. 2. In **Network locations**, go to **Virtual networks** and select **Manage**. @@ -51,7 +51,7 @@ First, create [virtual networks](/cloudflare-one/connections/connect-networks/pr - + 1. Create a [virtual network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) corresponding to one of your dedicated egress IPs. We recommend using a name related to the location of the corresponding dedicated egress IP. For example, if your users will egress from the Americas, you can name the virtual network `vnet-AMER`. @@ -78,7 +78,7 @@ First, create [virtual networks](/cloudflare-one/connections/connect-networks/pr After creating your virtual networks, route your private network CIDRs over each virtual network. This ensures that users can reach all services on your network regardless of which egress IP they use. - + 1. Go to **Networks** > **Tunnels**. 2. Select your tunnel routing `10.0.0.0/8`, then select **Configure**. @@ -93,7 +93,7 @@ After creating your virtual networks, route your private network CIDRs over each - + 1. Assign your first virtual network to your private network route. For example, assign `vnet-AMER` to your tunnel that routes `10.0.0.0/8`: @@ -144,7 +144,7 @@ Each tunnel connected to your private network should have each of your virtual n Next, assign your dedicated egress IPs to each virtual network using Gateway egress policies. - + 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Egress Policies**. @@ -166,7 +166,7 @@ Next, assign your dedicated egress IPs to each virtual network using Gateway egr - + 1. Add a Gateway egress policy that matches the corresponding virtual network. For example: diff --git a/src/content/docs/d1/examples/d1-and-remix.mdx b/src/content/docs/d1/examples/d1-and-remix.mdx index 6e6dcdafc7ed89..c38dc56062b4cf 100644 --- a/src/content/docs/d1/examples/d1-and-remix.mdx +++ b/src/content/docs/d1/examples/d1-and-remix.mdx @@ -27,7 +27,7 @@ The following example shows you how to define a Remix [`loader`](https://remix.r * Bindings are passed through on the `context.env` parameter passed to a `LoaderFunction`. * If you configured a [binding](/pages/functions/bindings/#d1-databases) named `DB`, then you would access D1's [client API](/d1/build-with-d1/d1-client-api/#query-statement-methods) methods via `context.env.DB`. - + ```ts import type { LoaderFunction } from "@remix-run/cloudflare"; diff --git a/src/content/docs/d1/examples/d1-and-sveltekit.mdx b/src/content/docs/d1/examples/d1-and-sveltekit.mdx index 4a5227ca0bab8e..99ea5d473c1ec5 100644 --- a/src/content/docs/d1/examples/d1-and-sveltekit.mdx +++ b/src/content/docs/d1/examples/d1-and-sveltekit.mdx @@ -31,7 +31,7 @@ The following example shows you how to create a server endpoint configured to qu The example also shows you how to configure both your app-wide types within `src/app.d.ts` to recognize your `D1Database` binding, import the `@sveltejs/adapter-cloudflare` adapter into `svelte.config.js`, and configure it to apply to all of your routes. - + ```ts import type { RequestHandler } from "@sveltejs/kit"; diff --git a/src/content/docs/data-localization/how-to/cache.mdx b/src/content/docs/data-localization/how-to/cache.mdx index e504823684e1c2..5704fd4fae8c3c 100644 --- a/src/content/docs/data-localization/how-to/cache.mdx +++ b/src/content/docs/data-localization/how-to/cache.mdx @@ -14,7 +14,7 @@ In the following sections, we will give you some details about how to configure To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that [eligible assets](/cache/concepts/default-cache-behavior/) are cached only in-region, follow these steps for the dashboard or API configuration: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account and zone. 2. Go to the **DNS** tab. @@ -24,7 +24,7 @@ To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/r - + 1. To create records with the API, use the [API POST](/api/operations/dns-records-for-a-zone-create-dns-record) command. 2. Run the [API POST](/data-localization/regional-services/get-started/#configure-regional-services-via-api) command on the hostname to create a `regional_hostnames` with a specific region. diff --git a/src/content/docs/data-localization/how-to/cloudflare-for-saas.mdx b/src/content/docs/data-localization/how-to/cloudflare-for-saas.mdx index d41aeffc5f9fa2..987a699975bb49 100644 --- a/src/content/docs/data-localization/how-to/cloudflare-for-saas.mdx +++ b/src/content/docs/data-localization/how-to/cloudflare-for-saas.mdx @@ -14,7 +14,7 @@ In the following sections, we will give you some details about how to configure To configure Regional Services for both hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and the fallback origin, follow these steps for the dashboard or API configuration: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account and zone. 2. Go to the **Custom Hostnames** tab. @@ -22,7 +22,7 @@ To configure Regional Services for both hostnames [proxied](/dns/manage-dns-reco - + 1. Set the [fallback record](/api/operations/custom-hostname-fallback-origin-for-a-zone-update-fallback-origin-for-custom-hostnames). 2. Create a [Custom Hostname](/api/operations/custom-hostname-for-a-zone-create-custom-hostname). diff --git a/src/content/docs/data-localization/how-to/load-balancing.mdx b/src/content/docs/data-localization/how-to/load-balancing.mdx index aeaf56615757d8..ccb4e9ae127218 100644 --- a/src/content/docs/data-localization/how-to/load-balancing.mdx +++ b/src/content/docs/data-localization/how-to/load-balancing.mdx @@ -16,7 +16,7 @@ You can load balance traffic at different levels of the networking stack dependi To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that the Load Balancer is available only in-region, follow these steps for the dashboard or API configuration: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account and zone. 2. Go to the **Load Balancing** tab. @@ -27,7 +27,7 @@ To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/r - + 1. Follow the instructions outlined to [create a load balancer](/load-balancing/load-balancers/create-load-balancer/#create-a-load-balancer) via API. 2. Run the [API POST](/data-localization/regional-services/get-started/#configure-regional-services-via-api) command on the Load Balancer hostname to create a `regional_hostnames` with a specific region. diff --git a/src/content/docs/data-localization/how-to/pages.mdx b/src/content/docs/data-localization/how-to/pages.mdx index e841fbf3b9f02c..c86abb92611e5d 100644 --- a/src/content/docs/data-localization/how-to/pages.mdx +++ b/src/content/docs/data-localization/how-to/pages.mdx @@ -14,7 +14,7 @@ In the following sections, we will give you some details about how to configure To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that processing of a Pages project occurs only in-region, follow these steps for the dashboard or API configuration: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account. 2. Go to the **Workers & Pages** tab. @@ -26,7 +26,7 @@ To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/r - + 1. Use the [API POST](/api/operations/pages-domains-add-domain) command to add a Custom Domain to a Pages project. 2. Run the [API POST](/data-localization/regional-services/get-started/#configure-regional-services-via-api) command on the Pages Custom Domain to create a `regional_hostnames` with a specific Region. diff --git a/src/content/docs/dns/dns-firewall/setup.mdx b/src/content/docs/dns/dns-firewall/setup.mdx index 7e5605a15b1ed9..00d2e2933bc9c3 100644 --- a/src/content/docs/dns/dns-firewall/setup.mdx +++ b/src/content/docs/dns/dns-firewall/setup.mdx @@ -25,7 +25,7 @@ Prior to setting up DNS Firewall, you need: ### Create a DNS Firewall cluster - + 1. Log in to the [Cloudflare account](https://dash.cloudflare.com) with DNS Firewall. 2. On the account homepage, click **DNS Firewall**. @@ -46,7 +46,7 @@ If you forget to save your new IP addresses, find your cluster and click **IP Ad ::: - + You can also create a DNS Firewall cluster by sending a [POST request](/api/operations/dns-firewall-create-dns-firewall-cluster) to the API. diff --git a/src/content/docs/dns/foundation-dns/setup.mdx b/src/content/docs/dns/foundation-dns/setup.mdx index 9c20bad3fd59ae..d323f452f2f0e6 100644 --- a/src/content/docs/dns/foundation-dns/setup.mdx +++ b/src/content/docs/dns/foundation-dns/setup.mdx @@ -18,14 +18,14 @@ To enable advanced nameservers on an existing zone: 1. Opt for advanced nameservers on your zone: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. 2. Go to **DNS** > **Records**. 3. In the **Cloudflare nameservers** card, enable **Advanced nameservers**. 4. After you refresh the page, the card will display the values for your advanced nameservers `NS` records. - + Use the [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) endpoint to send a PATCH request like the following: diff --git a/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx b/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx index 2f5ecc0a7a6d08..f203badf64cb2b 100644 --- a/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx +++ b/src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx @@ -26,7 +26,7 @@ If your domain is added to Cloudflare by a hosting partner, manage your DNS reco ## Create DNS records - + To create a DNS record in the dashboard: @@ -47,7 +47,7 @@ To create a DNS record in the dashboard: - + To create records with the API, use a [POST request](/api/operations/dns-records-for-a-zone-create-dns-record). For field definitions, select a record type under the request body specification. @@ -59,7 +59,7 @@ For specific API examples, refer to [DNS record types](/dns/manage-dns-records/r ## Edit DNS records - + To edit DNS records in the dashboard: @@ -71,7 +71,7 @@ To edit DNS records in the dashboard: - + To update part of a record with the API, use a [PATCH request](/api/operations/dns-records-for-a-zone-patch-dns-record). If you want to overwrite the entire existing record, use a [PUT request](/api/operations/dns-records-for-a-zone-update-dns-record). @@ -81,7 +81,7 @@ To update part of a record with the API, use a [PATCH request](/api/operations/d ## Delete DNS records - + To delete DNS records in the dashboard: @@ -93,7 +93,7 @@ To delete DNS records in the dashboard: - + To delete records with the API, use a [DELETE request](/api/operations/dns-records-for-a-zone-delete-dns-record). diff --git a/src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx b/src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx index 8880db642f0110..d258ab4aeae779 100644 --- a/src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx +++ b/src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx @@ -24,7 +24,7 @@ If you are using certain record types — for example, `CNAME`, `DNAME`, `MX`, ` ### Import zone file to Cloudflare - + To import a zone file using the dashboard: @@ -34,7 +34,7 @@ To import a zone file using the dashboard: 4. For **Import DNS records**, select your [formatted file](#format-your-zone-file). 5. If you do not want [applicable records](/dns/manage-dns-records/reference/proxied-dns-records/) proxied, unselect **Proxy imported DNS records**. - + To import records using the API, send a [POST request](/api/operations/dns-records-for-a-zone-import-dns-records) with a properly [formatted file](#format-your-zone-file). @@ -46,7 +46,7 @@ To import records using the API, send a [POST request](/api/operations/dns-recor You can also bulk export records from Cloudflare. - + To export records using the dashboard: @@ -55,7 +55,7 @@ To export records using the dashboard: 3. Select **Import and Export**. 4. Select **Export**. - + To export records using the API, send a [GET request](/api/operations/dns-records-for-a-zone-export-dns-records). diff --git a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx index 7da25f33b940ae..1286d0b347b908 100644 --- a/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx +++ b/src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx @@ -24,13 +24,13 @@ For example, for a zone `domain.test`, the ZCNS can be `ns1.domain.test` and `ns To create zone custom nameservers: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and zone. 2. Go to **DNS** > **Records**. 3. On **Custom Nameservers**, click **Add Custom Nameservers** and enter the subdomains used for the ZCNS names (for example, `ns1`, `ns2`, `ns3`). - + Use the [Edit zone endpoint](/api/operations/zones-0-patch) and specify the custom nameservers in the payload: @@ -59,13 +59,13 @@ If you are using [Cloudflare as a secondary DNS provider](/dns/zone-setups/zone- To remove zone custom nameservers (and their associated, read-only DNS records): - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and zone. 2. Go to **DNS** > **Records**. 3. On **Custom nameservers**, select **Remove custom nameservers**. - + Use the [Edit zone endpoint](/api/operations/zones-0-patch) and include an empty array in the payload: diff --git a/src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-secondary.mdx b/src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-secondary.mdx index e31ccf1934d798..df9f88dde51b82 100644 --- a/src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-secondary.mdx @@ -126,7 +126,7 @@ If you keep any DNS records that still refer `cdn.cloudflare.net`, HTTP traffic 3. Link your Cloudflare zone to the peer DNS server you just created. - + 1. Go to **DNS** > **Records**. 2. Under **DNS Zone Transfers**, select **Manage linked peers**. @@ -137,7 +137,7 @@ If you keep any DNS records that still refer `cdn.cloudflare.net`, HTTP traffic 4. Select the peer server you previously created. If needed, you can link more than one peer server to a zone. 5. Select **Save** to confirm. - + Use the [Update Secondary Zone Configuration endpoint](/api/operations/secondary-dns-\(-secondary-zone\)-update-secondary-zone-configuration) to link your Cloudflare zone to the peer DNS server. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx b/src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx index 6cfaafeb11d875..bd78a386a26a8e 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx @@ -18,7 +18,7 @@ You need to create an Access Control List (ACL) in certain situations: An ACL is configured at the account level, which means that it will apply to every primary and secondary zone in your account. - + To create a new ACL using the dashboard: @@ -31,7 +31,7 @@ To create a new ACL using the dashboard: * **IP range**: Enter a range of IPv4 or IPv6 addresses (limited to a maximum of /24 for IPv4 and /64 for IPv6). 6. Click **Create**. - + To create a new ACL using the API, send a [POST](/api/operations/secondary-dns-\(-acl\)-create-acl) request. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx index 47fae4e944cac0..a379dd58ae17cb 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx @@ -44,11 +44,11 @@ If using the API, you may also want to [locate your Zone and Account IDs](/funda - + - + @@ -61,7 +61,7 @@ You only need to create a peer DNS server if you want: * Your secondary nameservers to receive **NOTIFYs** for changes to your Cloudflare DNS records. * A **TSIG** to sign zone transfer requests and **NOTIFYs**. - + To create a peer using the dashboard: @@ -76,7 +76,7 @@ To create a peer using the dashboard: * **Link an existing TSIG**: If desired, link the TSIG you [previously created](#step-1---create-tsig-optional). 6. Select **Create**. - + To create a peer DNS server using the API, send a [POST](/api/operations/secondary-dns-\(-peer\)-create-peer) request. @@ -86,7 +86,7 @@ To create a peer DNS server using the API, send a [POST](/api/operations/seconda If you previously [created a peer DNS server](#step-2---create-peer-dns-server-optional), you should link it to your primary zone. - + To create a secondary zone using the dashboard: @@ -97,7 +97,7 @@ To create a secondary zone using the dashboard: 5. Select a peer. 6. Select **Save**. - + To link a primary zone to a peer using the API, send a [POST](/api/operations/secondary-dns-\(-primary-zone\)-create-primary-zone-configuration) request with the ID of the peer you [previously created](#step-2---create-peer-dns-server-optional). @@ -121,14 +121,14 @@ Using the information from your secondary DNS provider, [create `NS` records](/d By default, Cloudflare ignores `NS` records that are added to the zone apex. To modify this behaviour, enable [multi-provider DNS](/dns/nameservers/nameserver-options/#multi-provider-dns): - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login). 2. Select your account and zone. 3. Go to **DNS** > **Settings**. 4. Enable **Multi-provider DNS**. - + ```bash curl --request PATCH \ @@ -147,14 +147,14 @@ curl --request PATCH \ When you enable outgoing zone transfers, this will send a DNS NOTIFY message to your secondary DNS provider. - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login). 2. Select your account and zone. 3. Go to **DNS** > **Settings**. 4. For **Outgoing Zone Transfers**, switch the toggle to **On**. - + To enable outgoing zone transfers using the API, send a [POST](/api/operations/secondary-dns-\(-primary-zone\)-enable-outgoing-zone-transfers) request. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx index 65748ceba8095d..6a4d7098e207d5 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx @@ -31,7 +31,7 @@ If you use Cloudflare secondary nameservers as the only nameservers authoritativ In this setup, DNSSEC on your pirmary DNS provider does not need to be enabled. - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. @@ -41,7 +41,7 @@ In this setup, DNSSEC on your pirmary DNS provider does not need to be enabled. 4. - + 1. Use the [Edit DNSSEC Status endpoint](/api/operations/dnssec-edit-dnssec-status) and set a `status` of `active` for your zone. @@ -91,13 +91,13 @@ Pre-signed DNSSEC does not support [Secondary DNS Overrides](/dns/zone-setups/zo ::: - + a. Select your zone and go to **DNS** > **Settings**. b. Under **DNSSEC with Secondary DNS** select **Pre-signed**. - + Use the [Edit DNSSEC Status endpoint](/api/operations/dnssec-edit-dnssec-status) and set the `dnssec_presigned` value to `true`. diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx index 80879fcb2803bb..aa470d2aa2fdbd 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx @@ -39,14 +39,14 @@ Before you set up Secondary DNS override, make sure that you have: ## Set up Secondary DNS override - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. 2. Go to **DNS** > **Settings**. 3. Enable **Secondary DNS override**. 4. On **DNS** > **Records**, for specific `A`, `AAAA`, or `CNAME` records, [change](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) their **Proxy status** to **Proxied**. - + 1. To enable Secondary DNS override on a zone, use the following PATCH request: diff --git a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx index 7b7aa0854d9325..913b99e0ef01d4 100644 --- a/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx +++ b/src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup.mdx @@ -52,11 +52,11 @@ Get the following values from your Cloudflare account: - + - + @@ -68,7 +68,7 @@ Get the following values from your Cloudflare account: ## 3. Create the Secondary Zone - + To create a secondary zone using the dashboard: @@ -87,7 +87,7 @@ To create a secondary zone using the dashboard: ::: 10. Click **Initiate zone transfer**. - + To create a secondary zone using the API, send a [POST](/api/operations/secondary-dns-\(-secondary-zone\)-create-secondary-zone-configuration) request with the `type` parameter set to `"secondary"`. diff --git a/src/content/docs/durable-objects/examples/build-a-counter.mdx b/src/content/docs/durable-objects/examples/build-a-counter.mdx index 1fb3086c25c3f7..78d85aea7793c1 100644 --- a/src/content/docs/durable-objects/examples/build-a-counter.mdx +++ b/src/content/docs/durable-objects/examples/build-a-counter.mdx @@ -15,7 +15,7 @@ import { TabItem, Tabs } from "~/components" This example shows how to build a counter using Durable Objects and Workers with [RPC methods](/workers/runtime-apis/rpc) that can print, increment, and decrement a `name` provided by the URL query string parameter, for example, `?name=A`. - + ```js import { DurableObject } from "cloudflare:workers"; @@ -90,7 +90,7 @@ export class Counter extends DurableObject { } ``` - + ```ts import { DurableObject } from "cloudflare:workers"; diff --git a/src/content/docs/durable-objects/examples/build-a-rate-limiter.mdx b/src/content/docs/durable-objects/examples/build-a-rate-limiter.mdx index 0c8cc9c88a25c1..82dc77994ee85e 100644 --- a/src/content/docs/durable-objects/examples/build-a-rate-limiter.mdx +++ b/src/content/docs/durable-objects/examples/build-a-rate-limiter.mdx @@ -41,7 +41,7 @@ This example uses Durable Object's [Alarms API](/durable-objects/api/alarms) to The first implementation of a rate limiter is below: - + ```js import { DurableObject } from "cloudflare:workers"; @@ -116,7 +116,7 @@ export class RateLimiter extends DurableObject { ``` - + ```ts import { DurableObject } from "cloudflare:workers"; @@ -202,7 +202,7 @@ export class RateLimiter extends DurableObject { While the token bucket algorithm is popular for implementing rate limiting and uses Durable Object features, there is a simpler approach: - + ```js // Durable Object @@ -229,7 +229,7 @@ export class RateLimiter extends DurableObject { ``` - + ```ts title="index.ts" // Durable Object diff --git a/src/content/docs/durable-objects/examples/websocket-hibernation-server.mdx b/src/content/docs/durable-objects/examples/websocket-hibernation-server.mdx index 67700be1e1e110..812b6c43cada8d 100644 --- a/src/content/docs/durable-objects/examples/websocket-hibernation-server.mdx +++ b/src/content/docs/durable-objects/examples/websocket-hibernation-server.mdx @@ -25,7 +25,7 @@ WebSocket Hibernation is unavailable for outgoing WebSocket use cases. Hibernati ::: - + ```js import { DurableObject } from "cloudflare:workers"; @@ -99,7 +99,7 @@ export class WebSocketHibernationServer extends DurableObject { ``` - + ```ts import { DurableObject } from "cloudflare:workers"; diff --git a/src/content/docs/durable-objects/examples/websocket-server.mdx b/src/content/docs/durable-objects/examples/websocket-server.mdx index f1500c55792e5c..875cd92683dd4f 100644 --- a/src/content/docs/durable-objects/examples/websocket-server.mdx +++ b/src/content/docs/durable-objects/examples/websocket-server.mdx @@ -23,7 +23,7 @@ WebSocket connections pin your Durable Object to memory, and so duration charges ::: - + ```js import { DurableObject } from "cloudflare:workers"; @@ -102,7 +102,7 @@ export class WebSocketServer extends DurableObject { } ``` - + ```ts import { DurableObject } from "cloudflare:workers"; diff --git a/src/content/docs/durable-objects/get-started.mdx b/src/content/docs/durable-objects/get-started.mdx index 8a6149a97c5852..bd8bf3171483a7 100644 --- a/src/content/docs/durable-objects/get-started.mdx +++ b/src/content/docs/durable-objects/get-started.mdx @@ -55,7 +55,7 @@ If you do not use JavaScript or TypeScript, you will need a [shim](https://devel Your `MyDurableObject` class will have a constructor with two parameters. The first parameter, `state`, passed to the class constructor contains state specific to the Durable Object, including methods for accessing storage. The second parameter, `env`, contains any bindings you have associated with the Worker when you uploaded it. - + ```js export class MyDurableObject { @@ -63,7 +63,7 @@ export class MyDurableObject { } ``` - + ```ts export class MyDurableObject { @@ -77,7 +77,7 @@ Workers communicate with a Durable Object via the fetch API. Like a Worker, a Du Your file should now look like: - + ```js export class MyDurableObject { @@ -89,7 +89,7 @@ export class MyDurableObject { } ``` - + ```ts export class MyDurableObject { @@ -125,7 +125,7 @@ This is achieved by configuring a binding in the calling Worker for each Durable To communicate with a Durable Object, the fetch handler should look like the following: - + ```js export default { @@ -141,7 +141,7 @@ export default { }; ``` - + ```ts export default { diff --git a/src/content/docs/fundamentals/api/reference/permissions.mdx b/src/content/docs/fundamentals/api/reference/permissions.mdx index b519b27d863ece..3909e863e30d92 100644 --- a/src/content/docs/fundamentals/api/reference/permissions.mdx +++ b/src/content/docs/fundamentals/api/reference/permissions.mdx @@ -22,11 +22,11 @@ To obtain an updated list of token permissions, including the permission ID and The applicable scope of user permissions is `com.cloudflare.api.user`. - + - + @@ -36,11 +36,11 @@ The applicable scope of user permissions is `com.cloudflare.api.user`. The applicable scope of account permissions is `com.cloudflare.api.account`. - + - + @@ -50,11 +50,11 @@ The applicable scope of account permissions is `com.cloudflare.api.account`. The applicable scope of zone permissions is `com.cloudflare.api.account.zone`. - + - + diff --git a/src/content/docs/fundamentals/subscriptions-and-billing/change-plan.mdx b/src/content/docs/fundamentals/subscriptions-and-billing/change-plan.mdx index 6c694bd0994ce4..58d0e6d5ada4b6 100644 --- a/src/content/docs/fundamentals/subscriptions-and-billing/change-plan.mdx +++ b/src/content/docs/fundamentals/subscriptions-and-billing/change-plan.mdx @@ -24,7 +24,7 @@ For additional help, refer to [this Community thread](https://community.cloudfla ## Change plan type - + To change the Cloudflare plan for a domain in the dashboard: @@ -40,7 +40,7 @@ To change the Cloudflare plan for a domain in the dashboard: 5. Select **Confirm**. - + To change the Cloudflare plan for a domain using the API, first send a [`GET`](/api/operations/zone-rate-plan-list-available-plans) request to review available subscriptions. @@ -58,7 +58,7 @@ If you are an Enterprise customer and cannot change your plan type, contact your ## Change plan duration - + To change the duration of your Cloudflare plan in the dashboard: @@ -78,7 +78,7 @@ To change the duration of your Cloudflare plan in the dashboard: 6. Select **Confirm**. - + To change the duration of a Cloudflare plan for a domain using the API, send a [`PUT`](/api/operations/zone-subscription-update-zone-subscription) request with an updated value for the `frequency` parameter. diff --git a/src/content/docs/learning-paths/load-balancing/setup/create-monitor.mdx b/src/content/docs/learning-paths/load-balancing/setup/create-monitor.mdx index d33b25d819881e..0c532a5d531987 100644 --- a/src/content/docs/learning-paths/load-balancing/setup/create-monitor.mdx +++ b/src/content/docs/learning-paths/load-balancing/setup/create-monitor.mdx @@ -10,7 +10,7 @@ import { Render, TabItem, Tabs } from "~/components" - + Set up the monitor @@ -18,7 +18,7 @@ import { Render, TabItem, Tabs } from "~/components" Prepare your servers - + Set up the monitor diff --git a/src/content/docs/learning-paths/load-balancing/setup/create-pools.mdx b/src/content/docs/learning-paths/load-balancing/setup/create-pools.mdx index ef8387007df922..79245f2a67f396 100644 --- a/src/content/docs/learning-paths/load-balancing/setup/create-pools.mdx +++ b/src/content/docs/learning-paths/load-balancing/setup/create-pools.mdx @@ -10,13 +10,13 @@ import { Render, TabItem, Tabs } from "~/components" - + - + diff --git a/src/content/docs/learning-paths/load-balancing/setup/test-load-balancer.mdx b/src/content/docs/learning-paths/load-balancing/setup/test-load-balancer.mdx index 9842567bb90c5f..482c5e655cfbc5 100644 --- a/src/content/docs/learning-paths/load-balancing/setup/test-load-balancer.mdx +++ b/src/content/docs/learning-paths/load-balancing/setup/test-load-balancer.mdx @@ -12,11 +12,11 @@ import { Render, TabItem, Tabs } from "~/components" ## Create a load balancer - + - + diff --git a/src/content/docs/learning-paths/replace-vpn/build-policies/create-policy.mdx b/src/content/docs/learning-paths/replace-vpn/build-policies/create-policy.mdx index 4247c5003b459c..f5c924d91a46b4 100644 --- a/src/content/docs/learning-paths/replace-vpn/build-policies/create-policy.mdx +++ b/src/content/docs/learning-paths/replace-vpn/build-policies/create-policy.mdx @@ -20,7 +20,7 @@ To create a new policy, open [Zero Trust](https://one.dash.cloudflare.com/) and ## Example DNS policy - + | Traffic Selector | Operator | Value | | ---------------- | -------- | ---------------------- | @@ -36,7 +36,7 @@ To create a new policy, open [Zero Trust](https://one.dash.cloudflare.com/) and - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ @@ -83,7 +83,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ ## Example network policy - + | Traffic Selector | Operator | Value | | ---------------- | -------- | ------------------ | @@ -99,7 +99,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ @@ -144,7 +144,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ We recommend adding a catch-all policy to the bottom of your network policy list. An effective Zero Trust model should prioritize default-deny actions to avoid any overly permissive policy building. For example, - + | Traffic Selector | Operator | Value | Logic | | ---------------- | -------- | ---------------------------- | ----- | @@ -157,7 +157,7 @@ We recommend adding a catch-all policy to the bottom of your network policy list - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/deploy-egress-ips.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/deploy-egress-ips.mdx index 14eddbd893b23a..16541b5e589c07 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/deploy-egress-ips.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/build-egress-policies/deploy-egress-ips.mdx @@ -28,7 +28,7 @@ One of the most common use cases for egress policies is to ensure a consistent e We recommend building baseline egress policies that can cover a majority of your use cases without making policy management overly complex. If all of your users need to access a series of applications that all require a specific egress IP, you should build a policy explicit to those users (or to all of your users) to ensure that all of their traffic egresses using those egress IPs. For example, you can define specific egress IPs for users with access to financial data: - + | Selector | Operator | Value | Egress method | | ---------------- | -------- | --------------- | ----------------------------------- | @@ -40,7 +40,7 @@ We recommend building baseline egress policies that can cover a majority of your - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/browser-isolation.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/browser-isolation.mdx index 377a88d4424388..5dd8e85cc80f4d 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/browser-isolation.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/browser-isolation.mdx @@ -24,7 +24,7 @@ As you have begun deploying Cloudflare Zero Trust, you may have started to visua You can control potential risk and shape user behavior without applying heavy-handed block policies by applying policies to isolate user traffic to applications that match your defined categories. You can then set additional parameters in the policy, such as the ability to restrict copy/paste and upload/download. Users can still access information in the tools -- if not use the tools to a lesser extent -- while you minimize the risk of data loss. - + 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Firewall Policies**. @@ -45,7 +45,7 @@ You can control potential risk and shape user behavior without applying heavy-ha 6. Select **Create policy**. - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ @@ -94,7 +94,7 @@ You can accomplish this by creating the following policies: In this context, if some traffic is unknown to your organization, Cloudflare will isolate it by default. Cloudflare will also prevent any malicious code from being executed client side, with additional controls available. - + * Allow known applications and websites: @@ -114,7 +114,7 @@ In this context, if some traffic is unknown to your organization, Cloudflare wil | -------- | ------------- | ----- | ------- | | Host | matches regex | `.*` | Isolate | - + ```bash title="Allow known applications and websites" curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/data-loss-prevention.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/data-loss-prevention.mdx index 9cd7f51e3ed712..6472fcb8902052 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/data-loss-prevention.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/data-loss-prevention.mdx @@ -34,14 +34,14 @@ If your organization is most concerned about general data patterns that fit exis To help this better match the needs of your organization, you can also build a complex profile that matches data to both an existing library and a custom string detection or database. For example: - + | Selector | Operator | Value | Logic | Action | | ----------- | -------- | ------------------------- | ----- | ------ | | DLP Profile | in | *Credentials and Secrets* | Or | Block | | DLP Profile | in | *AWS Key Dataset* | | | - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ @@ -76,7 +76,7 @@ To validate your regex, use [Rustexp](https://rustexp.lpil.uk/). For example, you can use a custom expression to detect when your users share product SKUs in the format `CF1234-56789`: - + 1. [Build a custom profile](#build-a-custom-profile) with the following custom entry: @@ -93,7 +93,7 @@ For example, you can use a custom expression to detect when your users share pro - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ @@ -144,7 +144,7 @@ The best way to start applying data loss prevention to your traffic, minimize th Many organizations want to detect and log financial information egressing from user devices to critical SaaS applications. To limit the risk of false positives and to filter out logging noise, Cloudflare recommends building your first series of policies to specify both target data and target destination. For example, you can block financial information from being sent to AI chatbots, such as ChatGPT and Gemini: - + | Selector | Operator | Value | Logic | Action | | ------------------ | -------- | ------------------------- | ----- | ------ | @@ -153,7 +153,7 @@ Many organizations want to detect and log financial information egressing from u - + ```bash title="Block financial information shared with AI" curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ diff --git a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/tls-inspection.mdx b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/tls-inspection.mdx index 239d0840497c17..141db20fc3f891 100644 --- a/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/tls-inspection.mdx +++ b/src/content/docs/learning-paths/secure-internet-traffic/build-http-policies/tls-inspection.mdx @@ -64,14 +64,14 @@ You can build pass-through rules to accommodate any type of device or user group For example, if users are issued a corporate-managed iPhone with limited permissions, set an additional Do Not Inspect policy for all traffic matching the device posture value. That could include the OS type, OS version, or a list of serial numbers (updated via the API with hooks from your MDM tool) for those iPhones: - + | Selector | Operator | Value | Logic | Action | | --------------------- | -------- | --------------------------------------- | ----- | -------------- | | Passed Device Posture | in | *iOS 17 or higher (OS version)* | And | Do Not Inspect | | Passed Device Posture | in | *iPhone Serial Numbers (Serial number)* | | | - + 1. Create a list of device serial numbers that you do not want to inspect. @@ -131,13 +131,13 @@ For example, if users are issued a corporate-managed iPhone with limited permiss If you filter your network-connected devices with Magic WAN tunnels, the WARP Connector, or other devices that do not have the Cloudflare certificate installed, you will need to accommodate by creating pass-through policies. For these devices, you should explicitly exempt TLS inspection for the source network IP range from which that traffic will be originating. For example: - + | Selector | Operator | Value | Action | | ------------------ | -------- | ---------------- | -------------- | | Source Internal IP | in | `203.0.113.0/24` | Do Not Inspect | - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ diff --git a/src/content/docs/learning-paths/zero-trust-web-access/advanced-workflows/isolate-application.mdx b/src/content/docs/learning-paths/zero-trust-web-access/advanced-workflows/isolate-application.mdx index 4fda5a0d9d7f28..6064232d517963 100644 --- a/src/content/docs/learning-paths/zero-trust-web-access/advanced-workflows/isolate-application.mdx +++ b/src/content/docs/learning-paths/zero-trust-web-access/advanced-workflows/isolate-application.mdx @@ -52,7 +52,7 @@ with HTTP policies applied"] **Policy 1: Allow employees who pass device posture checks** - + | Action | Rule type | Selector | Value | | ------ | --------- | ------------------------------------------------------------------------------------------------------- | -------------------------- | @@ -65,7 +65,7 @@ with HTTP policies applied"] - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/access/apps/{app_uuid}/policies \ @@ -100,7 +100,7 @@ To create a list of serial numbers, refer to [Create Zero Trust list](/api/opera **Policy 2: Allow and isolate contractors** - + | Action | Rule type | Selector | Value | | ------ | --------- | ---------------- | ------------------------------- | @@ -112,7 +112,7 @@ To create a list of serial numbers, refer to [Create Zero Trust list](/api/opera - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/access/apps/{app_uuid}/policies \ @@ -149,7 +149,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/access/apps/{app Prevents users on unmanaged devices from downloading any files from your private application. - + | Selector | Operator | Value | Logic | Action | | ---------------------------- | -------- | -------------------------- | ----- | ------- | @@ -162,7 +162,7 @@ Prevents users on unmanaged devices from downloading any files from your private - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ @@ -238,7 +238,7 @@ Block users on unmanaged devices from downloading files that contain credit card * **Policy 2: Block credit card numbers** - + | Selector | Operator | Value | Logic | Action | | -------------------------------------------------------------------------- | -------- | -------------------------- | ----- | ------ | @@ -248,7 +248,7 @@ Block users on unmanaged devices from downloading files that contain credit card - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/rules \ diff --git a/src/content/docs/load-balancing/get-started/quickstart.mdx b/src/content/docs/load-balancing/get-started/quickstart.mdx index 2043757ebb7635..5027266970eaa5 100644 --- a/src/content/docs/load-balancing/get-started/quickstart.mdx +++ b/src/content/docs/load-balancing/get-started/quickstart.mdx @@ -28,7 +28,7 @@ Make sure you: - + Set up the monitor @@ -36,7 +36,7 @@ Make sure you: Prepare your servers - + Set up the monitor @@ -56,13 +56,13 @@ Make sure you: - + - + @@ -84,11 +84,11 @@ Make sure you: - + - + diff --git a/src/content/docs/load-balancing/load-balancers/create-load-balancer.mdx b/src/content/docs/load-balancing/load-balancers/create-load-balancer.mdx index 272aee7af6d2d0..f91afb6990e43b 100644 --- a/src/content/docs/load-balancing/load-balancers/create-load-balancer.mdx +++ b/src/content/docs/load-balancing/load-balancers/create-load-balancer.mdx @@ -16,11 +16,11 @@ For more details about load balancers, refer to [Load balancers](/load-balancing ## Create a load balancer - + - + @@ -44,7 +44,7 @@ Sharing load balancers across sites is only supported if the target zone is on a ## Edit a load balancer - + To edit a load balancer in the dashboard: @@ -53,7 +53,7 @@ To edit a load balancer in the dashboard: 3. While going through the [creation workflow](#create-a-load-balancer), update settings as needed. 4. On the **Review** step, click **Save**. - + When you edit a load balancer with the API, your request type depends on how much you want to edit. @@ -67,14 +67,14 @@ To update specific settings without having to resubmit the entire configuration, If you delete or disable a load balancer, your endpoint's response to requests will depend on your [existing DNS records](/load-balancing/load-balancers/dns-records/#disabling-a-load-balancer). - + To delete a load balancer in the dashboard: 1. Go to **Traffic** > **Load Balancing**. 2. On a specific load balancer, click **Delete**. - + To delete a load balancer using the API, send a [DELETE](/api/operations/load-balancers-delete-load-balancer) request. diff --git a/src/content/docs/load-balancing/local-traffic-management/ltm-tunnels-setup.mdx b/src/content/docs/load-balancing/local-traffic-management/ltm-tunnels-setup.mdx index 50f5591a9a4b05..ca75bb1e58ca3e 100644 --- a/src/content/docs/load-balancing/local-traffic-management/ltm-tunnels-setup.mdx +++ b/src/content/docs/load-balancing/local-traffic-management/ltm-tunnels-setup.mdx @@ -18,7 +18,7 @@ The specific configuration steps can vary depending on your infrastructure and s 2. [Deploy the tunnel](/cloudflare-one/connections/connect-networks/deploy-tunnels/) to connect to your data center. 3. Create a [virtual network](/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks/) and assign it to the tunnel you configured in the previous steps. - + To create a virtual network: @@ -68,13 +68,13 @@ The specific configuration will vary depending on your use case. Refer to the fo - + - + To get a list of your current virtual networks, use the [List virtual networks](/api/operations/tunnel-virtual-network-list-virtual-networks) API operation. diff --git a/src/content/docs/load-balancing/monitors/create-monitor.mdx b/src/content/docs/load-balancing/monitors/create-monitor.mdx index c4eaab11bf5f6d..4e7cf51f5753f4 100644 --- a/src/content/docs/load-balancing/monitors/create-monitor.mdx +++ b/src/content/docs/load-balancing/monitors/create-monitor.mdx @@ -18,7 +18,7 @@ For more details about monitors, refer to [Monitors](/load-balancing/monitors/). ## Create a monitor - + **Set up the monitor** @@ -46,7 +46,7 @@ Once your monitor is created, you need to attach it to a pool: 5. Select **Save**. The status of your health monitor will be *unknown* until the results of the first check are available. - + **Set up the monitor** @@ -66,7 +66,7 @@ Once your monitor is created, save its `id` property. Include this value in the ## Edit a monitor - + To edit a monitor in the dashboard: @@ -76,7 +76,7 @@ To edit a monitor in the dashboard: 4. Update settings as needed. 5. Select **Save**. - + When you edit a monitor with the API, your request type depends on how much you want to edit. @@ -88,7 +88,7 @@ To update specific settings without having to resubmit the entire configuration, ## Delete a monitor - + To delete a monitor in the dashboard: @@ -96,7 +96,7 @@ To delete a monitor in the dashboard: 2. Select **Manage Monitors**. 3. On a specific monitor, select **Delete**. - + To delete a monitor using the API, send a [DELETE](/api/operations/account-load-balancer-monitors-delete-monitor) request. diff --git a/src/content/docs/load-balancing/pools/create-pool.mdx b/src/content/docs/load-balancing/pools/create-pool.mdx index 3d25a675ffe8b3..11dc65aa6dcc8b 100644 --- a/src/content/docs/load-balancing/pools/create-pool.mdx +++ b/src/content/docs/load-balancing/pools/create-pool.mdx @@ -24,11 +24,11 @@ For more background information on pools, refer to [Pools](/load-balancing/pools ## Create a pool - + - + @@ -38,7 +38,7 @@ For more background information on pools, refer to [Pools](/load-balancing/pools ## Edit a pool - + To edit a pool in the dashboard: @@ -48,7 +48,7 @@ To edit a pool in the dashboard: 4. Update settings as needed. 5. Click **Save**. - + When you edit a pool with the API, your request type depends on how much you want to edit. @@ -69,7 +69,7 @@ If you get an error when trying to delete a pool, consider the hostnames listed If the pool is referenced by geo steering, the configuration is **not** automatically removed when you change to a different **Traffic Steering** method. To make sure you remove it, select **Geo Steering**, remove the pool, and then apply and save any other necessary changes. ::: - + To delete a pool in the dashboard: @@ -77,7 +77,7 @@ To delete a pool in the dashboard: 2. Click **Manage Pools**. 3. On a specific pool, click **Delete**. - + To delete a pool using the API, send a [DELETE](/api/operations/account-load-balancer-pools-delete-pool) request. diff --git a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/geo-steering.mdx b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/geo-steering.mdx index 35f34a36702231..cee32df7be42c1 100644 --- a/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/geo-steering.mdx +++ b/src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/geo-steering.mdx @@ -28,7 +28,7 @@ Cloudflare has [13 geographic regions](/load-balancing/reference/region-mapping- If you add a pool to a region, you cannot [delete this pool](/load-balancing/pools/create-pool/#delete-a-pool) until you remove it from the **Geo steering** configuration. The configuration is **not** automatically removed when you change to a different **Traffic Steering** method. ::: - + When [creating or editing a load balancer](/load-balancing/load-balancers/create-load-balancer/): @@ -40,7 +40,7 @@ When [creating or editing a load balancer](/load-balancing/load-balancers/create 6. If adding multiple pools, re-order them into your preferred failback order. 7. (optional) Add more regions if needed. - + Use the `regions_pool` property of the [Update Load Balancers](/api/operations/load-balancers-update-load-balancer) command to specify an array of regions. Specify each region using the [appropriate region code](/load-balancing/reference/region-mapping-api/#list-of-load-balancer-regions) followed by a list of endpoints to use for that region. @@ -69,7 +69,7 @@ If you only define `WNAM`, then traffic from the East Coast will be routed to th ### Country steering - + When [creating or editing a load balancer](/load-balancing/load-balancers/create-load-balancer/): @@ -81,7 +81,7 @@ When [creating or editing a load balancer](/load-balancing/load-balancers/create 6. If adding multiple pools, re-order them into your preferred failback order. 7. (optional) Add more countries if needed. - + When creating a load balancer [via the API](/api/operations/load-balancers-create-load-balancer), include the `country_pools` object to map countries to a list of pool IDs (ordered by their failover priority). diff --git a/src/content/docs/logs/log-explorer.mdx b/src/content/docs/logs/log-explorer.mdx index faaf396e6b5103..bd6943f0f0c021 100644 --- a/src/content/docs/logs/log-explorer.mdx +++ b/src/content/docs/logs/log-explorer.mdx @@ -43,7 +43,7 @@ Alternatively, API tokens with Account and Zone level Logs Edit permissions can You can use the dashboard or the API to enable the datasets you want to query with Log Explorer. - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. 2. Go to **Analytics & Logs** > **Log Explorer**. @@ -54,7 +54,7 @@ You can use the dashboard or the API to enable the datasets you want to query wi It may take a few minutes for the logs to become available for querying. ::: - + Use the Log Explorer API to enable Log Explorer for each dataset you wish to store. It may take up to 30 minutes after a logstream is enabled before you can view the logs. @@ -89,7 +89,7 @@ curl https://api.cloudflare.com/client/v4/zones/{zone_id}/logs/explorer/datasets Filtering and viewing your logs is available via the Cloudflare Dashboard or via query API. - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain. 2. Go to **Analytics & Logs** > **Log Explorer**. @@ -108,7 +108,7 @@ You can also access the Log Explorer dashboard directly from the [Security Analy ::: - + Log Explorer exposes a query endpoint that uses a familiar SQL syntax for querying your logs generated with Cloudflare's network. diff --git a/src/content/docs/magic-firewall/how-to/enable-ids.mdx b/src/content/docs/magic-firewall/how-to/enable-ids.mdx index fa575906cb94ce..d7d426472c2d85 100644 --- a/src/content/docs/magic-firewall/how-to/enable-ids.mdx +++ b/src/content/docs/magic-firewall/how-to/enable-ids.mdx @@ -19,13 +19,13 @@ You can enable IDS through the dashboard or via the API. This feature is available for Advanced Magic Firewall users. For access, contact your account team. ::: - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. 2. Select **Magic Firewall** > **IDS**. 3. Enable IDS. - + To start using IDS via the API, first create a new ruleset in the `magic-transit-ids-managed` phase with a rule which is enabled. diff --git a/src/content/docs/magic-firewall/packet-captures/collect-pcaps.mdx b/src/content/docs/magic-firewall/packet-captures/collect-pcaps.mdx index 46d7f78f520ae4..0d04067cf86716 100644 --- a/src/content/docs/magic-firewall/packet-captures/collect-pcaps.mdx +++ b/src/content/docs/magic-firewall/packet-captures/collect-pcaps.mdx @@ -41,7 +41,7 @@ For help determining which data center to select for a packet capture, visit [ht * `byte_limit`: The minimum value is `1` byte and maximum value is `1000000000` bytes. - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select you account. 2. Select **Magic Transit** or **Magic WAN**. @@ -52,7 +52,7 @@ For help determining which data center to select for a packet capture, visit [ht The main **Packet captures** page displays a list of captures. - + The PCAPs API needs both `system` and `type` to be specified to start a capture. A PCAP's `system` is the product or logical subsystem where packets are captured, and a PCAP's `type` is how the captured packets are built into a PCAP file. @@ -170,14 +170,14 @@ The response is a JSON body that contains the details of the job running to buil ## Check packet capture status - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select you account. 2. Select **Magic Transit** or **Magic WAN**. 3. In **Packet captures**, select **Start a capture**. 4. Select the **Captures** tab. - + To check the status of a running job, send a request to the endpoint and specify the PCAP identifier. The PCAP identifier is received in the response of a collect request as shown in the previous step. @@ -225,7 +225,7 @@ The capture status displays one of the following options: After your request finishes processing, you can download your packet captures. - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select you account. 2. Select **Magic Transit** or **Magic WAN**. @@ -235,7 +235,7 @@ After your request finishes processing, you can download your packet captures. Packet captures are available to download when the **Status** displays **Success**. - + For more information on how to process multiple saved capture files into a single output file, refer to [Wireshark's mergecap documentation](https://www.wireshark.org/docs/man-pages/mergecap.html). @@ -258,7 +258,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/pcaps/{pcap_id}/ ## List packet captures - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select you account. 2. Select **Magic Transit** or **Magic WAN**. @@ -267,7 +267,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/pcaps/{pcap_id}/ The list of packet captures associated with your account displays. - + To view a list of sent requests, use the following command: diff --git a/src/content/docs/magic-firewall/packet-captures/pcaps-bucket-setup.mdx b/src/content/docs/magic-firewall/packet-captures/pcaps-bucket-setup.mdx index 6e8e6bfa351629..bf6739f9fbed1c 100644 --- a/src/content/docs/magic-firewall/packet-captures/pcaps-bucket-setup.mdx +++ b/src/content/docs/magic-firewall/packet-captures/pcaps-bucket-setup.mdx @@ -16,7 +16,7 @@ You can configure an Amazon S3 or Google Cloud Platform bucket to use as a targe Learn how to set up a bucket for use with full packet captures. - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select you account. 2. Select **Magic Transit** or **Magic WAN**. @@ -28,7 +28,7 @@ Learn how to set up a bucket for use with full packet captures. The **Prove ownership** step of the **Bucket configuration** displays. - + Before you can begin using a bucket, you must first enable destinations. @@ -42,7 +42,7 @@ Next, validate the bucket and confirm ownership. After the initial bucket set up, you need to confirm you own the bucket via an ownership challenge. After you validate your bucket, you can begin using it to collect full packet captures. - + 1. From the **Prove ownership** step of the **Bucket configuration**, locate the **Ownership token** field. 2. In the **Ownership token** field, enter the ownership token for your service provider. @@ -50,7 +50,7 @@ After the initial bucket set up, you need to confirm you own the bucket via an o The **Buckets** tab displays a list of the buckets associated with your account. Refer to the **Status** column to see the status of your bucket configuration. - + The `bucket` field should be the URI of the bucket. For Amazon S3, the `bucket` field is in the form `s3:///?region=`, and for Google Cloud Storage the form is `gs:///`. @@ -125,7 +125,7 @@ The bucket status displays one of the following options: View a list of all buckets configured on your account. - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select you account. 2. Select **Magic Transit** or **Magic WAN**. @@ -134,7 +134,7 @@ View a list of all buckets configured on your account. The list of buckets associated with your account displays. - + ```bash title="Bucket list request example" curl https://api.cloudflare.com/client/v4/accounts/{account_id}/pcaps/ownership \ diff --git a/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay.mdx b/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay.mdx index 708d18fd686d01..8cb434fdc06705 100644 --- a/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay.mdx +++ b/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay.mdx @@ -27,7 +27,7 @@ accTitle: An example of Connector in DHCP Relay mode To configure DHCP relay: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. 2. Go to **Magic WAN** > **Sites**. @@ -39,7 +39,7 @@ To configure DHCP relay: 8. In **Upstream DHCP server addresses**, enter the IP address of your DHCP server. 9. (Optional) If you need to add more DHCP server addresses, select **Add upstream DHCP server address** as many times as needed, and enter the new values. - + diff --git a/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-server.mdx b/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-server.mdx index 88826cdb4af72e..8d11ba1932dba2 100644 --- a/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-server.mdx +++ b/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-server.mdx @@ -8,7 +8,7 @@ import { Render, TabItem, Tabs } from "~/components" When you use a static IP address, Magic WAN Connector can also act as a DHCP server in your network. To enable this feature: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. 2. Go to **Magic WAN** > **Sites**. @@ -30,7 +30,7 @@ When you use a static IP address, Magic WAN Connector can also act as a DHCP ser - + diff --git a/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation.mdx b/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation.mdx index ab7fa8ff6e1835..2c4887c51a6c46 100644 --- a/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation.mdx +++ b/src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation.mdx @@ -8,7 +8,7 @@ import { Render, TabItem, Tabs } from "~/components" If you configure your Connector to be a DHCP server, you can also assign IP addresses to specific devices on your network. To reserve IP addresses: - + 1. Configure your Connector to be a [DHCP server](/magic-wan/configuration/connector/network-options/dhcp/dhcp-server/). 2. Select **Add DHCP Reservation**. @@ -16,7 +16,7 @@ If you configure your Connector to be a DHCP server, you can also assign IP addr 4. In **IP Address**, enter the IP address for that device. 5. (Optional) If you need to reserve more IP addresses, select **Add DHCP Reservation** as many times as needed, and enter the new values. - + diff --git a/src/content/docs/magic-wan/configuration/connector/network-options/network-segmentation.mdx b/src/content/docs/magic-wan/configuration/connector/network-options/network-segmentation.mdx index 3e268a86901275..c18d76559fd2f1 100644 --- a/src/content/docs/magic-wan/configuration/connector/network-options/network-segmentation.mdx +++ b/src/content/docs/magic-wan/configuration/connector/network-options/network-segmentation.mdx @@ -36,7 +36,7 @@ The following guide assumes you have already created a site and configured your ## Create a policy - + Follow the steps below to create a new LAN policy to segment your network. Only the fields marked **required** are mandatory. @@ -54,7 +54,7 @@ Follow the steps below to create a new LAN policy to segment your network. Only 12. In **Traffic path**, select **Forwarded via Cloudflare** if you want traffic to be forwarded to Cloudflare to be processed. If you do not select this option, traffic will flow locally, in your premises without passing through Cloudflare. 13. Select **Create policy**. - + @@ -150,7 +150,7 @@ The new policy will ensure that traffic between the specified LANs flows locally ## Edit a policy - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. 2. Select **Magic WAN** > **Sites**. @@ -160,7 +160,7 @@ The new policy will ensure that traffic between the specified LANs flows locally 6. Select the policy you need to edit > **Edit**. 7. Make your changes, and select **Update policy**. - + @@ -210,7 +210,7 @@ https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id} ## Delete a policy - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. 2. Select **Magic WAN** > **Sites**. @@ -221,7 +221,7 @@ https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id} 7. Select **Delete**. 8. Select **I understand that deleting a policy is permanent** in the dialog box > **Delete**. - + diff --git a/src/content/docs/network/ip-geolocation.mdx b/src/content/docs/network/ip-geolocation.mdx index a37ff6a41c1b13..5ebb1caaabf217 100644 --- a/src/content/docs/network/ip-geolocation.mdx +++ b/src/content/docs/network/ip-geolocation.mdx @@ -21,7 +21,7 @@ The recommended procedure to enable IP geolocation information is to [enable the If you only want the request header for the visitor's country, you can enable **IP Geolocation**. - + To enable **IP Geolocation** in the dashboard: @@ -29,7 +29,7 @@ To enable **IP Geolocation** in the dashboard: 2. Go to **Network**. 3. For **IP Geolocation**, switch the toggle to **On**. - + To enable **IP Geolocation** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `ip_geolocation` as the setting name in the URI path, and the `value` parameter set to `"on"`. diff --git a/src/content/docs/network/ipv6-compatibility.mdx b/src/content/docs/network/ipv6-compatibility.mdx index f80ab47887f1fd..9c67814004a55f 100644 --- a/src/content/docs/network/ipv6-compatibility.mdx +++ b/src/content/docs/network/ipv6-compatibility.mdx @@ -33,7 +33,7 @@ If your origin web server only understands IPv4 formatted IP addresses, non-Ente Alternatively, customers with an Enterprise account can disable Cloudflare's IPv6 compatibility. - + To disable **IPv6 Compatibility** in the dashboard: @@ -41,7 +41,7 @@ To disable **IPv6 Compatibility** in the dashboard: 2. Go to **Network**. 3. For **IPv6 Compatibility**, switch the toggle to **Off**. - + To disable **IPv6 Compatibility** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `ipv6` as the setting name in the URI path, and the `value` parameter set to `"off"`. diff --git a/src/content/docs/network/onion-routing.mdx b/src/content/docs/network/onion-routing.mdx index e4b1b2fcdad028..78dbadb6988bfd 100644 --- a/src/content/docs/network/onion-routing.mdx +++ b/src/content/docs/network/onion-routing.mdx @@ -32,7 +32,7 @@ You should note that the visible domain in the UI remains unchanged, as the host ## Enable Onion Routing - + To enable **Onion Routing** in the dashboard: @@ -40,7 +40,7 @@ To enable **Onion Routing** in the dashboard: 2. Go to **Network**. 3. For **Onion Routing**, switch the toggle to **On**. - + To enable **Onion Routing** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `opportunistic_onion` as the setting name in the URI path, and the `value` parameter set to `"on"`. diff --git a/src/content/docs/network/pseudo-ipv4.mdx b/src/content/docs/network/pseudo-ipv4.mdx index f0fc7cf8c4739d..a443abc75ebc82 100644 --- a/src/content/docs/network/pseudo-ipv4.mdx +++ b/src/content/docs/network/pseudo-ipv4.mdx @@ -43,7 +43,7 @@ your origin web server. To configure **Pseudo IPv4**: - + To change the **Pseudo IPv4** setting in the dashboard: @@ -51,7 +51,7 @@ To change the **Pseudo IPv4** setting in the dashboard: 2. Go to **Network**. 3. For **Pseudo IPv4**, choose your desired setting. - + To change **Pseudo IPv4** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `pseudo_ipv4` as the setting name in the URI path, and the `value` parameter set to your desired value: `"off"`, `"add_header"`, or `"overwrite_header"`. diff --git a/src/content/docs/network/response-buffering.mdx b/src/content/docs/network/response-buffering.mdx index 13ab43b8199956..45d31fdce09ee2 100644 --- a/src/content/docs/network/response-buffering.mdx +++ b/src/content/docs/network/response-buffering.mdx @@ -21,7 +21,7 @@ If your domain sends many small packets, however, it might be faster to **buffer ## Enable Response Buffering - + To enable **Response Buffering** in the dashboard: @@ -29,7 +29,7 @@ To enable **Response Buffering** in the dashboard: 2. Go to **Network**. 3. For **Response Buffering**, switch the toggle to **On**. - + To enable **Response Buffering** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `response_buffering` as the setting name in the URI path, and the `value` parameter set to `"on"`. diff --git a/src/content/docs/network/websockets.mdx b/src/content/docs/network/websockets.mdx index 3efa45a2e00679..3d6f0e0bba7da6 100644 --- a/src/content/docs/network/websockets.mdx +++ b/src/content/docs/network/websockets.mdx @@ -19,7 +19,7 @@ WebSockets are open connections sustained between the client and the origin serv ## Enable WebSockets - + To enable **WebSockets** connections to your origin server in the dashboard: @@ -27,7 +27,7 @@ To enable **WebSockets** connections to your origin server in the dashboard: 2. Go to **Network**. 3. For **WebSockets**, switch the toggle to **On**. - + To enable **WebSockets** connections to your origin server with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `websockets` as the setting name in the URI path, and the `value` parameter set to `"on"`. diff --git a/src/content/docs/page-shield/reference/roles-and-permissions.mdx b/src/content/docs/page-shield/reference/roles-and-permissions.mdx index f81a594293d1b0..298f0c63c9ae13 100644 --- a/src/content/docs/page-shield/reference/roles-and-permissions.mdx +++ b/src/content/docs/page-shield/reference/roles-and-permissions.mdx @@ -24,12 +24,12 @@ Cloudflare users with the following [roles](/fundamentals/setup/manage-members/r To interact with the [Page Shield API](/page-shield/reference/page-shield-api/) you need an API token with one of the following [permissions](/fundamentals/api/reference/permissions/): - + * Page Shield > Edit * Page Shield > Read *(read-only access)* - + * Page Shield Write * Page Shield Read *(read-only access)* diff --git a/src/content/docs/pages/framework-guides/deploy-a-hono-site.mdx b/src/content/docs/pages/framework-guides/deploy-a-hono-site.mdx index 3e351c1d866cce..e799994aa8e7f7 100644 --- a/src/content/docs/pages/framework-guides/deploy-a-hono-site.mdx +++ b/src/content/docs/pages/framework-guides/deploy-a-hono-site.mdx @@ -53,7 +53,7 @@ There are different alternatives to fix this issue. For example, you can configu Open your `package.json` file and update the `scripts` section: - + ```json "scripts": { @@ -65,7 +65,7 @@ Open your `package.json` file and update the `scripts` section: }, ``` - + ```json "scripts": { diff --git a/src/content/docs/pages/framework-guides/deploy-a-nuxt-site.mdx b/src/content/docs/pages/framework-guides/deploy-a-nuxt-site.mdx index 5bc4ee835efa16..b3ffa4a60ce440 100644 --- a/src/content/docs/pages/framework-guides/deploy-a-nuxt-site.mdx +++ b/src/content/docs/pages/framework-guides/deploy-a-nuxt-site.mdx @@ -138,7 +138,7 @@ In Nuxt, add server-side code via [Server Routes and Middleware](https://nuxt.co The following code block shows an example of accessing a KV namespace in Nuxt. - + ```javascript null {2} export default defineEventHandler(({ context }) => { @@ -150,7 +150,7 @@ export default defineEventHandler(({ context }) => { }); ``` - + ```typescript null {2} export default defineEventHandler(({ context }) => { diff --git a/src/content/docs/pages/functions/advanced-mode.mdx b/src/content/docs/pages/functions/advanced-mode.mdx index 7001cccaa9d33c..5d8f9f34422943 100644 --- a/src/content/docs/pages/functions/advanced-mode.mdx +++ b/src/content/docs/pages/functions/advanced-mode.mdx @@ -20,7 +20,7 @@ In advanced mode, your Function will assume full control of all incoming HTTP re After making a `_worker.js` file in your output directory, add the following code snippet: - + ```js export default { @@ -37,7 +37,7 @@ export default { } ``` - + ```ts // Note: You would need to compile your TS into JS and output it as a `_worker.js` file. We do not read `_worker.ts` diff --git a/src/content/docs/pages/functions/bindings.mdx b/src/content/docs/pages/functions/bindings.mdx index f39e949a45e1e6..808e8fb2d64c35 100644 --- a/src/content/docs/pages/functions/bindings.mdx +++ b/src/content/docs/pages/functions/bindings.mdx @@ -38,7 +38,7 @@ To configure a KV namespace binding via the Cloudflare dashboard: Below is an example of how to use KV in your Function. In the following example, your KV namespace binding is called `TODO_LIST` and you can access the binding in your Function code on `context.env`: - + ```js export async function onRequest(context) { @@ -47,7 +47,7 @@ export async function onRequest(context) { } ``` - + ```ts interface Env { @@ -97,7 +97,7 @@ To configure a Durable Object binding via the Cloudflare dashboard: Below is an example of how to use Durable Objects in your Function. In the following example, your DO binding is called `DURABLE_OBJECT` and you can access the binding in your Function code on `context.env`: - + ```js export async function onRequestGet(context) { @@ -109,7 +109,7 @@ export async function onRequestGet(context) { } ``` - + ```ts interface Env { @@ -160,7 +160,7 @@ To configure a R2 bucket binding via the Cloudflare dashboard: Below is an example of how to use R2 buckets in your Function. In the following example, your R2 bucket binding is called `BUCKET` and you can access the binding in your Function code on `context.env`: - + ```js export async function onRequest(context) { @@ -172,7 +172,7 @@ export async function onRequest(context) { } ``` - + ```ts interface Env { @@ -233,7 +233,7 @@ To configure a D1 database binding via the Cloudflare dashboard: Below is an example of how to use D1 in your Function. In the following example, your D1 database binding is `NORTHWIND_DB` and you can access the binding in your Function code on `context.env`: - + ```js export async function onRequest(context) { @@ -245,7 +245,7 @@ export async function onRequest(context) { } ``` - + ```ts interface Env { @@ -312,7 +312,7 @@ To configure a Vectorize index binding via the Cloudflare dashboard: To use Vectorize index in your Pages Function, you can access your Vectorize index binding in your Pages Function code. In the following example, your Vectorize index binding is called `VECTORIZE_INDEX` and you can access the binding in your Pages Function code on `context.env`. - + ```js // Sample vectors: 3 dimensions wide. @@ -346,7 +346,7 @@ export async function onRequest(context) { } ``` - + ```ts export interface Env { @@ -409,7 +409,7 @@ To configure a Workers AI binding via the Cloudflare dashboard: To use Workers AI in your Pages Function, you can access your Workers AI binding in your Pages Function code. In the following example, your Workers AI binding is called `AI` and you can access the binding in your Pages Function code on `context.env`. - + ```js export async function onRequest(context) { @@ -421,7 +421,7 @@ export async function onRequest(context) { } ``` - + ```ts interface Env { @@ -474,7 +474,7 @@ To configure a Service binding via the Cloudflare dashboard: Below is an example of how to use Service bindings in your Function. In the following example, your Service binding is called `SERVICE` and you can access the binding in your Function code on `context.env`: - + ```js export async function onRequestGet(context) { @@ -482,7 +482,7 @@ export async function onRequestGet(context) { } ``` - + ```ts interface Env { @@ -529,7 +529,7 @@ To configure a queue producer binding via the Cloudflare dashboard: Below is an example of how to use a queue producer binding in your Function. In this example, the binding is named `MY_QUEUE` and you can access the binding in your Function code on `context.env`:: - + ```js export async function onRequest(context) { @@ -543,7 +543,7 @@ export async function onRequest(context) { } ``` - + ```ts interface Env { @@ -585,7 +585,7 @@ To configure an Analytics Engine binding via the Cloudflare dashboard: Below is an example of how to use an Analytics Engine binding in your Function. In the following example, the binding is called `ANALYTICS_ENGINE` and you can access the binding in your Function code on `context.env`: - + ```js export async function onRequest(context) { @@ -601,7 +601,7 @@ export async function onRequest(context) { } ``` - + ```ts interface Env { @@ -643,7 +643,7 @@ To configure an environment variable via the Cloudflare dashboard: Below is an example of how to use environment variables in your Function. The environment variable in this example is `ENVIRONMENT` and you can access the environment variable on `context.env`: - + ```js export function onRequest(context) { @@ -655,7 +655,7 @@ export function onRequest(context) { } ``` - + ```ts interface Env { diff --git a/src/content/docs/pulumi/tutorial/add-site.mdx b/src/content/docs/pulumi/tutorial/add-site.mdx index 69c4ce1fef1427..36f8af4e7b6488 100644 --- a/src/content/docs/pulumi/tutorial/add-site.mdx +++ b/src/content/docs/pulumi/tutorial/add-site.mdx @@ -68,21 +68,21 @@ A Pulumi program is code written in a [supported programming language](https://g To create a program, select your language of choice and run the `pulumi` command: - + ```sh $ pulumi new javascript --name addsite-cloudflare --yes # wait a few seconds while the project is initialized ``` - + ```sh $ pulumi new typescript --name addsite-cloudflare --yes # wait a few seconds while the project is initialized ``` - + ```sh $ pulumi new python --name addsite-cloudflare --yes @@ -184,21 +184,21 @@ You will now add the Pulumi Cloudflare package and a Cloudflare Zone resource to ### a. Install dependencies - + ```sh $ npm install @pulumi/cloudflare added 1 package ... ``` - + ```sh $ npm install @pulumi/cloudflare added 1 package ... ``` - + ```sh $ echo "pulumi_cloudflare>=5.35,<6.0.0" >> requirements.txt @@ -259,7 +259,7 @@ There are no dependencies to download for YAML. Skip ahead. Replace the contents of your entrypoint file with the following: - + ```js "use strict"; @@ -282,7 +282,7 @@ const zone = new cloudflare.Zone("my-zone", { exports.zoneId = zone.id; ``` - + ```typescript import * as pulumi from "@pulumi/pulumi"; @@ -304,7 +304,7 @@ const zone = new cloudflare.Zone("my-zone", { export const zoneId = zone.id; ``` - + ```py import pulumi @@ -478,21 +478,21 @@ This process makes Cloudflare your authoritative DNS provider, allowing your DNS Towards the end of your entrypoint file, below the `zoneId` variable, add the following: - + ```js exports.nameservers = zone.nameServers; exports.status = zone.status; ``` - + ```typescript export const nameservers = zone.nameServers; export const status = zone.status; ``` - + ```py pulumi.export('nameservers', zone.name_servers) @@ -585,7 +585,7 @@ You will now add a DNS record to your domain. Below is the final version of how your Pulumi program entrypoint file should look. Replace the contents of your entrypoint file with the following: - + ```js "use strict"; @@ -618,7 +618,7 @@ const record = new cloudflare.Record("my-record", { }); ``` - + ```typescript import * as pulumi from "@pulumi/pulumi"; @@ -655,7 +655,7 @@ const record = new cloudflare.Record("my-record", { }); ``` - + ```py import pulumi diff --git a/src/content/docs/rules/page-rules/manage.mdx b/src/content/docs/rules/page-rules/manage.mdx index bac24649b21665..f41438c1e2f09a 100644 --- a/src/content/docs/rules/page-rules/manage.mdx +++ b/src/content/docs/rules/page-rules/manage.mdx @@ -17,7 +17,7 @@ You can manage Page Rules in the Cloudflare dashboard or via API. ## Create a page rule - + To create a page rule in the dashboard: @@ -34,7 +34,7 @@ To create a page rule in the dashboard: For ideas about what rules you can create, refer to [recommended rules](/rules/page-rules/reference/recommended-rules/). - + To create a page rule using the API, send a [`POST` request](/api/operations/page-rules-create-a-page-rule). @@ -52,7 +52,7 @@ You may also want to review the documentation on [wildcard matching](/rules/page ## Edit a page rule - + To edit a page rule in the dashboard: @@ -63,7 +63,7 @@ To edit a page rule in the dashboard: * To enable or disable the rule, select the on/off toggle. * To modify the URL pattern, settings, and order, select **Edit** (wrench icon). Then, enter the information you want to change. - + To update one or more fields using the API, send a [`PATCH` request](/api/operations/page-rules-edit-a-page-rule). @@ -73,7 +73,7 @@ To entirely replace the configuration of a page rule, send a [`PUT` request](/ap ## Delete a page rule - + To delete a page rule in the dashboard: @@ -81,7 +81,7 @@ To delete a page rule in the dashboard: 2. Go to **Rules** > **Page Rules**. 3. For a specific rule, select **X**. Then, select **Delete**. - + To delete a page rule using the API, send a [`DELETE` request](/api/operations/page-rules-delete-a-page-rule). diff --git a/src/content/docs/rules/reference/page-rules-migration/index.mdx b/src/content/docs/rules/reference/page-rules-migration/index.mdx index 9987892b697b57..3848b72c3c2fbc 100644 --- a/src/content/docs/rules/reference/page-rules-migration/index.mdx +++ b/src/content/docs/rules/reference/page-rules-migration/index.mdx @@ -127,7 +127,7 @@ The following table summarizes how different Page Rules settings will be migrate ### Migrate Always Use HTTPS - + **Context:** @@ -169,7 +169,7 @@ You configured a Page Rule to perform an automatic redirect from HTTP to HTTPS f ### Migrate Automatic HTTPS Rewrites - + **Context:** @@ -211,7 +211,7 @@ You configured a Page Rule turning on Automatic HTTPS Rewrites for all subdomain ### Migrate Browser Cache TTL - + **Context:** @@ -256,7 +256,7 @@ You configured a Page Rule adjusting browser cache TTL to one day for all subdom ### Migrate Browser Integrity Check - + **Context:** @@ -298,7 +298,7 @@ You configured a Page Rule turning on Browser Integrity Check for all subdomains ### Migrate Bypass Cache on Cookie - + **Context:** @@ -341,7 +341,7 @@ You configured a Page Rule turning on Bypass Cache on Cookie for all subdomains ### Migrate Cache By Device Type - + **Context:** @@ -386,7 +386,7 @@ You configured a Page Rule turning on Cache By Device Type for all subdomains of ### Migrate Cache Deception Armor - + **Context:** @@ -430,7 +430,7 @@ You configured a Page Rule turning on Cache Deception Armor for all subdomains o ### Migrate Cache Level (Cache Everything) - + **Context:** @@ -473,7 +473,7 @@ You configured a Page Rule turning on caching of all assets for all subdomains o ### Migrate Cache on Cookie - + **Context:** @@ -516,7 +516,7 @@ You configured a Page Rule turning on caching for responses that contained cooki ### Migrate Cache TTL by status code - + **Context:** @@ -567,7 +567,7 @@ You configured a Page Rule turning on caching of every response with status code ### Migrate Custom Cache Key - + **Context:** @@ -612,7 +612,7 @@ You configured a Page Rule setting a custom cache key for all query string param ### Migrate Disable Apps - + **Context:** @@ -659,7 +659,7 @@ The **Disable Performance** setting is deprecated. Any Page Rules with this sett This Page Rules setting turned off Mirage, Polish, and Rocket Loader. You can still turn on or off relevant Cloudflare features one by one using Configuration Rules. - + **Context:** @@ -708,7 +708,7 @@ The **Disable Security** setting is deprecated. Any Page Rules with this setting This Page Rules setting turns off Email Obfuscation, Rate Limiting (previous version), Scrape Shield, URL (Zone) Lockdown, and WAF managed rules (previous version). You can still turn on or off relevant Cloudflare features one by one using Configuration Rules and WAF custom rules. - + **Context:** @@ -741,7 +741,7 @@ If you are still using WAF managed rules (previous version) or Rate Limiting (pr ### Migrate Disable Zaraz - + **Context:** @@ -781,7 +781,7 @@ You configured a Page Rule turning off [Zaraz](/zaraz/) for all subdomains of `e ### Migrate Edge Cache TTL - + **Context:** @@ -827,7 +827,7 @@ You configured a Page Rule adjusting Edge Cache TTL for all subdomains of `examp ### Migrate Email Obfuscation - + **Context:** @@ -871,7 +871,7 @@ You configured a Page Rule turning off [Email Obfuscation](/waf/tools/scrape-shi **Example #1: Redirect `www` to root domain** - + **Context:** @@ -915,7 +915,7 @@ You configured a Page Rule permanently redirecting `www.example.com` to `example **Example #2: Redirect all pages under old path to new path** - + **Context:** @@ -960,7 +960,7 @@ You configured a Page Rule permanently redirecting `example.com/old-path` to `ex ### Migrate Host Header Override - + **Context:** @@ -1002,7 +1002,7 @@ You configured a Page Rule changing the `Host` HTTP header to `example.saas-prov ### Migrate IP Geolocation Header - + **Context:** @@ -1028,7 +1028,7 @@ You configured a Page Rule adding a `CF-IPCountry` HTTP header, for all requests ### Migrate Mirage - + **Context:** @@ -1070,7 +1070,7 @@ You configured a Page Rule turning off Mirage for all subdomains of `example.com ### Migrate Opportunistic Encryption - + **Context:** @@ -1112,7 +1112,7 @@ You configured a Page Rule turning off Opportunistic Encryption for all subdomai ### Migrate Origin Cache Control - + **Context:** @@ -1157,7 +1157,7 @@ You configured a Page Rule turning off Origin Cache Control for all subdomains o ### Migrate Origin Error Page Pass-thru - + **Context:** @@ -1202,7 +1202,7 @@ You configured a Page Rule turning on Origin Error Page Pass-thru for all subdom ### Migrate Polish - + **Context:** @@ -1244,7 +1244,7 @@ You configured a Page Rule turning off [Polish](/images/polish/) for all subdoma ### Migrate Query String Sort - + **Context:** @@ -1289,7 +1289,7 @@ You configured a Page Rule turning on Query String Sort for all subdomains of `e ### Migrate Resolve Override - + **Context:** @@ -1330,7 +1330,7 @@ You configured a Page Rule changing the origin to `example.saas-provider.com`, f ### Migrate Respect Strong ETags - + **Context:** @@ -1375,7 +1375,7 @@ You configured a Page Rule turning on byte-for-byte equivalency checks for all s ### Migrate Rocket Loader - + **Context:** @@ -1417,7 +1417,7 @@ You configured a Page Rule turning off Rocket Loader for all subdomains of `exam ### Migrate Security Level - + **Context:** @@ -1459,7 +1459,7 @@ You configured a Page Rule setting Security Level to *I'm Under Attack* for all ### Migrate True Client IP Header - + **Context:** @@ -1485,7 +1485,7 @@ You configured a Page Rule adding a `True-Client-IP` HTTP header for all request ### Migrate SSL - + **Context:** diff --git a/src/content/docs/rules/transform/managed-transforms/configure.mdx b/src/content/docs/rules/transform/managed-transforms/configure.mdx index dc266e8c3a6d10..58512e18a07d63 100644 --- a/src/content/docs/rules/transform/managed-transforms/configure.mdx +++ b/src/content/docs/rules/transform/managed-transforms/configure.mdx @@ -10,7 +10,7 @@ description: Learn how to configure Managed Transforms. import { Details, TabItem, Tabs } from "~/components" - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and website. @@ -20,7 +20,7 @@ import { Details, TabItem, Tabs } from "~/components" 4. Enable or disable the [desired Managed Transforms](/rules/transform/managed-transforms/reference/) by selecting the toggle next to each entry. The Cloudflare dashboard will only list available Managed Transforms according to your Cloudflare plan and product subscriptions. - + **1. Get list of available Managed Transforms** diff --git a/src/content/docs/speed/optimization/content/prefetch-urls.mdx b/src/content/docs/speed/optimization/content/prefetch-urls.mdx index 417becb738b707..137c3ff53b1fbc 100644 --- a/src/content/docs/speed/optimization/content/prefetch-urls.mdx +++ b/src/content/docs/speed/optimization/content/prefetch-urls.mdx @@ -24,7 +24,7 @@ For Cloudflare to start prefetching URLs, you will need to [enable the feature]( ### Enable Prefetch URLs - + To enable **Prefetch URLs** in the dashboard: @@ -32,7 +32,7 @@ To enable **Prefetch URLs** in the dashboard: 2. Go to **Speed** > **Optimization** > **Content Optimization**. 3. For **Prefetch URLs**, switch the toggle to **On**. - + To enable or disable **Prefetch URLs** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `prefetch_preload` as the setting name in the URI path, and the `value` parameter set to your desired setting (`"on"` or `"off"`). diff --git a/src/content/docs/speed/optimization/content/rocket-loader/enable.mdx b/src/content/docs/speed/optimization/content/rocket-loader/enable.mdx index 7073b8d8f26847..ccf4479f5ef133 100644 --- a/src/content/docs/speed/optimization/content/rocket-loader/enable.mdx +++ b/src/content/docs/speed/optimization/content/rocket-loader/enable.mdx @@ -13,7 +13,7 @@ import { Render, TabItem, Tabs } from "~/components" To enable or disable Rocket Loader, use the following instructions. - + To enable or disable **Rocket Loader** in the dashboard: @@ -24,7 +24,7 @@ To enable or disable **Rocket Loader** in the dashboard: - + To enable or disable **Rocket Loader** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `rocket_loader` as the setting name in the URI path, and the `value` parameter set to `"on"` or `"off"`. diff --git a/src/content/docs/speed/optimization/protocol/0-rtt-connection-resumption.mdx b/src/content/docs/speed/optimization/protocol/0-rtt-connection-resumption.mdx index 4016caa3e3a110..1cd99ac3b9db1f 100644 --- a/src/content/docs/speed/optimization/protocol/0-rtt-connection-resumption.mdx +++ b/src/content/docs/speed/optimization/protocol/0-rtt-connection-resumption.mdx @@ -22,7 +22,7 @@ For more details on what 0-RTT is, how it works, and potential limitations, refe By default, 0-RTT Connection Resumption is not enabled on your Cloudflare application. - + To enable 0-RTT Connection Resumption in the dashboard: @@ -30,7 +30,7 @@ To enable 0-RTT Connection Resumption in the dashboard: 2. Navigate to **Speed > Optimization**. 3. Navigate to the **Protocol Optimization** tab and under **0-RTT Connection Resumption**, switch the toggle to **On**. - + To adjust your 0-RTT Connection Resumption settings with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `0rtt` as the setting name in the URI path, and the `value` parameter set to `"on"` or `"off"`. diff --git a/src/content/docs/speed/optimization/protocol/enhanced-http2-prioritization.mdx b/src/content/docs/speed/optimization/protocol/enhanced-http2-prioritization.mdx index ad1e4c0d043dae..a2cbfadc9ccd06 100644 --- a/src/content/docs/speed/optimization/protocol/enhanced-http2-prioritization.mdx +++ b/src/content/docs/speed/optimization/protocol/enhanced-http2-prioritization.mdx @@ -24,7 +24,7 @@ For more details, refer to [the introductory blog post](https://blog.cloudflare. ## Enable Enhanced HTTP/2 Prioritization - + To enable **Enhanced HTTP/2 Prioritization** in the Cloudflare dashboard: @@ -34,7 +34,7 @@ To enable **Enhanced HTTP/2 Prioritization** in the Cloudflare dashboard: 4. Go to **Protocol Optimization**. 5. For **Enhanced HTTP/2 Prioritization**, switch the toggle to **On**. - + To enable **Enhanced HTTP/2 Prioritization** using the Cloudflare API, send a [`PATCH` request](/api/operations/zone-settings-edit-single-setting) with `h2_prioritization` as the setting name in the URI path, and the `value` parameter set to `"on"`. diff --git a/src/content/docs/speed/optimization/protocol/http2.mdx b/src/content/docs/speed/optimization/protocol/http2.mdx index bd521e59d12dca..3a48c4200bb47d 100644 --- a/src/content/docs/speed/optimization/protocol/http2.mdx +++ b/src/content/docs/speed/optimization/protocol/http2.mdx @@ -30,7 +30,7 @@ HTTP/2 is enabled by default for all plans (though it does require an [SSL certi Domains on Free plans cannot disable Cloudflare's HTTP/2 setting. - + To disable **HTTP/2** in the dashboard: @@ -40,7 +40,7 @@ To disable **HTTP/2** in the dashboard: 4. Go to **Protocol Optimization**. 5. For **HTTP/2**, switch the toggle to **Off**. - + To disable **HTTP/2** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `http2` as the setting name in the URI path, and the `value` parameter set to `"off"`. diff --git a/src/content/docs/speed/optimization/protocol/http3.mdx b/src/content/docs/speed/optimization/protocol/http3.mdx index 7340bfd1815f03..1cd72fb838a53c 100644 --- a/src/content/docs/speed/optimization/protocol/http3.mdx +++ b/src/content/docs/speed/optimization/protocol/http3.mdx @@ -26,7 +26,7 @@ For more background on HTTP/3, visit the [Learning Center](https://www.cloudflar HTTP/3 is available to all plans (though it does require an [SSL certificate at Cloudflare’s edge network](/ssl/get-started/)). - + To enable **HTTP/3** in the dashboard: @@ -36,7 +36,7 @@ To enable **HTTP/3** in the dashboard: 4. Go to **Protocol Optimization**. 5. For **HTTP/3**, switch the toggle to **On**. - + To enable **HTTP/3** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `http3` as the setting name in the URI path, and the `value` parameter set to `"on"`. diff --git a/src/content/docs/ssl/edge-certificates/additional-options/always-use-https.mdx b/src/content/docs/ssl/edge-certificates/additional-options/always-use-https.mdx index 27a1245795dcde..48f9ab237273e6 100644 --- a/src/content/docs/ssl/edge-certificates/additional-options/always-use-https.mdx +++ b/src/content/docs/ssl/edge-certificates/additional-options/always-use-https.mdx @@ -33,7 +33,7 @@ To redirect traffic for all subdomains and hosts in your application, you can en If only some parts of your application can support HTTPS traffic, do not enable **Always Use HTTPS** and use a [dynamic redirect](/rules/url-forwarding/single-redirects/) to selectively perform the redirect to HTTPS. Refer to [Redirect admin area requests to HTTPS](/rules/url-forwarding/examples/redirect-admin-https/) for an example. ::: - + To enable **Always Use HTTPS** in the dashboard: @@ -42,7 +42,7 @@ To enable **Always Use HTTPS** in the dashboard: 3. Go to **SSL/TLS** > **Edge Certificates**. 4. For **Always Use HTTPS**, switch the toggle to **On**. - + To enable or disable **Always Use HTTPS** with the API: diff --git a/src/content/docs/ssl/edge-certificates/additional-options/automatic-https-rewrites.mdx b/src/content/docs/ssl/edge-certificates/additional-options/automatic-https-rewrites.mdx index 55cf8ca09c1957..900f3496053bb9 100644 --- a/src/content/docs/ssl/edge-certificates/additional-options/automatic-https-rewrites.mdx +++ b/src/content/docs/ssl/edge-certificates/additional-options/automatic-https-rewrites.mdx @@ -30,7 +30,7 @@ For security reasons, this feature will run on URLs pointing to `localhost` if t ## Enable Automatic HTTPS Rewrites - + To enable **Automatic HTTPS Rewrites** in the dashboard: @@ -38,7 +38,7 @@ To enable **Automatic HTTPS Rewrites** in the dashboard: 2. Go to **SSL/TLS** > **Edge Certificates**. 3. For **Automatic HTTPS Rewrites**, switch the toggle to **On**. - + To enable or disable **Automatic HTTPS Rewrites** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `automatic_https_rewrites` as the setting name in the URI path, and the `value` parameter set to your desired setting (`"on"` or `"off"`). diff --git a/src/content/docs/ssl/edge-certificates/additional-options/http-strict-transport-security.mdx b/src/content/docs/ssl/edge-certificates/additional-options/http-strict-transport-security.mdx index 6b19f126f9d17c..23962d419605dc 100644 --- a/src/content/docs/ssl/edge-certificates/additional-options/http-strict-transport-security.mdx +++ b/src/content/docs/ssl/edge-certificates/additional-options/http-strict-transport-security.mdx @@ -54,7 +54,7 @@ If you remove HTTPS before disabling HSTS or before waiting for the duration of ## Enable HSTS - + To enable HSTS using the dashboard: @@ -67,7 +67,7 @@ To enable HSTS using the dashboard: 7. Configure the [HSTS settings](#configuration-settings). 8. Select **Save**. - + To enable HSTS with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `security_header` as the setting name in the URI path, and specify the `value` object that includes your HSTS settings. diff --git a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx index 6fe162c3622536..3838cb9c16d075 100644 --- a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx +++ b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx @@ -42,14 +42,14 @@ If you have an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-ce To manage the TLS version applied to your whole zone when proxied through Cloudflare: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account. 2. Select your website. 3. Go to **SSL/TLS** > **Edge Certificates**. 4. For **Minimum TLS Version**, select an option. - + Use the [Edit zone setting](/api/operations/zone-settings-edit-single-setting) endpoint with `min_tls_version` as the setting name in the URI path, and specify your preferred minimum version in the `value` parameter. diff --git a/src/content/docs/ssl/edge-certificates/additional-options/opportunistic-encryption.mdx b/src/content/docs/ssl/edge-certificates/additional-options/opportunistic-encryption.mdx index dc0dd713a32e5a..ffac539ee31c35 100644 --- a/src/content/docs/ssl/edge-certificates/additional-options/opportunistic-encryption.mdx +++ b/src/content/docs/ssl/edge-certificates/additional-options/opportunistic-encryption.mdx @@ -18,7 +18,7 @@ Use HTTPS when both strong encryption and authentication are required. HTTP Oppo You do not need to configure your origin web server to support Opportunistic Encryption. All it requires is updating your settings in the Cloudflare dashboard. - + To enable Opportunistic Encryption in the dashboard: @@ -26,7 +26,7 @@ To enable Opportunistic Encryption in the dashboard: 2. Go to **SSL/TLS** > **Edge Certificates**. 3. For **Opportunistic Encryption**, switch the toggle to **On**. - + To adjust your Opportunistic Encryption settings with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `opportunistic_encryption` as the setting name in the URI path, and specify the `value` parameter with your desired setting (`"on"` or `"off"`). diff --git a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx index 3631bdd0d6a3df..0f33c1324e61c2 100644 --- a/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx +++ b/src/content/docs/ssl/edge-certificates/additional-options/tls-13.mdx @@ -26,7 +26,7 @@ TLS 1.3 requires a two-step activation: in the Cloudflare dashboard and in the b ### Enable TLS 1.3 in Cloudflare settings - + To enable TLS 1.3 in the dashboard: @@ -34,7 +34,7 @@ To enable TLS 1.3 in the dashboard: 2. Go to **SSL/TLS** > **Edge Certificates**. 3. For **TLS 1.3**, switch the toggle to **On**. - + To adjust your TLS 1.3 settings with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `tls_1_3` as the setting name in the URI path, and set the `value` parameter to your desired setting (`"on"` or `"off"`). diff --git a/src/content/docs/ssl/edge-certificates/additional-options/total-tls/enable.mdx b/src/content/docs/ssl/edge-certificates/additional-options/total-tls/enable.mdx index 9db5d782214185..290d82529fc670 100644 --- a/src/content/docs/ssl/edge-certificates/additional-options/total-tls/enable.mdx +++ b/src/content/docs/ssl/edge-certificates/additional-options/total-tls/enable.mdx @@ -13,7 +13,7 @@ import { Render, TabItem, Tabs } from "~/components" To enable [Total TLS](/ssl/edge-certificates/additional-options/total-tls/) - which issues individual certificates for your proxied hostnames - follow these instructions: - + To enable Total TLS in the dashboard: @@ -22,7 +22,7 @@ To enable Total TLS in the dashboard: 3. Go to **SSL/TLS** > **Edge Certificates**. 4. For **Total TLS**, switch the toggle to **On** and - if desired - choose an issuing **Certificate Authority**. - + To enable Total TLS with the API, send a [`PATCH`](/api/operations/total-tls-enable-or-disable-total-tls) request with the `enabled` parameter set to your desired setting (`true` or `false`). diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx index fb0cc11ec6da87..8acf8df6d38ce4 100644 --- a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx +++ b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx @@ -17,7 +17,7 @@ If you are using an existing [Universal SSL certificate](/ssl/edge-certificates/ Once you order a certificate, you can review the [certificate's status](/ssl/reference/certificate-statuses/) in the dashboard at **SSL/TLS** > **Edge Certificates** or via the API with a [GET request](/api/operations/certificate-packs-list-certificate-packs). - + To create a new advanced certificate in the dashboard: @@ -32,7 +32,7 @@ To create a new advanced certificate in the dashboard: * Certificate Validity Period 6. Select **Save**. - + To create a new certificate using the API, send a [POST request](/api/operations/certificate-packs-order-advanced-certificate-manager-certificate-pack) to the Cloudflare API. @@ -50,7 +50,7 @@ To create a new certificate using the API, send a [POST request](/api/operations ## Delete a certificate - + To delete an advanced certificate in the dashboard: @@ -59,7 +59,7 @@ To delete an advanced certificate in the dashboard: 3. Select a certificate. 4. Select **Delete Certificate**. - + To delete a certificate using the API, send a [DELETE request](/api/operations/certificate-packs-delete-advanced-certificate-manager-certificate-pack) to the Cloudflare API. diff --git a/src/content/docs/ssl/edge-certificates/caa-records.mdx b/src/content/docs/ssl/edge-certificates/caa-records.mdx index 3b090b1b1847b6..8d18478ec0a067 100644 --- a/src/content/docs/ssl/edge-certificates/caa-records.mdx +++ b/src/content/docs/ssl/edge-certificates/caa-records.mdx @@ -37,7 +37,7 @@ You should [create CAA records](#create-caa-records) in Cloudflare if each of th Create a CAA record for each Certificate Authority (CA) that you plan to use for your domain. - + To add a CAA record in the dashboard, @@ -51,7 +51,7 @@ To add a CAA record in the dashboard, 8. Select **Save**. 9. Repeat for each CA associated with your domain. - + To create a CAA record via the API, use this [POST endpoint](/api/operations/dns-records-for-a-zone-create-dns-record). diff --git a/src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/txt.mdx b/src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/txt.mdx index 53c927679ae9e3..5960f8bd94ed3f 100644 --- a/src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/txt.mdx +++ b/src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/txt.mdx @@ -31,13 +31,13 @@ Generally, you need to perform TXT-based DCV when your certificate [requires DCV - + - + diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/uploading.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/uploading.mdx index 709fc00bc6d902..c238d2dd33988b 100644 --- a/src/content/docs/ssl/edge-certificates/custom-certificates/uploading.mdx +++ b/src/content/docs/ssl/edge-certificates/custom-certificates/uploading.mdx @@ -39,7 +39,7 @@ Each custom certificate you upload must: ## Upload a custom certificate - + To upload a custom SSL certificate in the dashboard: @@ -76,7 +76,7 @@ To upload a custom SSL certificate in the dashboard: - + The following call will upload a certificate for use with `app.example.com`. Cloudflare will automatically bundle the certificate with a certificate chain optimized for maximum compatibility with browsers. @@ -166,7 +166,7 @@ If you are on an Enterprise plan and want to update a custom (modern) certificat Replacing a custom certificate following these steps does not lead to any downtime. No connections will be terminated and new connections will use the new certificate. The old certificate will only actually be deleted when the new certificate is uploaded and active. - + To update a certificate in the dashboard: @@ -177,7 +177,7 @@ To update a certificate in the dashboard: 5. Select the wrench icon and select **Replace SSL certificate and key**. 6. Follow the same steps as [upload a new certificate](#upload-a-custom-certificate). - + To update a certificate using the API, send a [`PATCH`](/api/operations/custom-ssl-for-a-zone-edit-ssl-configuration) command. diff --git a/src/content/docs/ssl/edge-certificates/geokey-manager/setup.mdx b/src/content/docs/ssl/edge-certificates/geokey-manager/setup.mdx index 13c18a08f77413..7ff26eda0fb3d5 100644 --- a/src/content/docs/ssl/edge-certificates/geokey-manager/setup.mdx +++ b/src/content/docs/ssl/edge-certificates/geokey-manager/setup.mdx @@ -80,7 +80,7 @@ For more information on the `policy` field, refer to [Supported options](/ssl/ed - + To use Geo Key Manager in the dashboard: @@ -94,7 +94,7 @@ To use Geo Key Manager in the dashboard: - + To use Geo Key Manager with the API, generally, follow the steps to [upload a custom certificate](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate). diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx index bc89d7cefddd2c..70a20901573e41 100644 --- a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx +++ b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx @@ -33,7 +33,7 @@ If you disable Universal SSL, you may experience errors with the following scena Before you disable Universal SSL/TLS, make sure you have [uploaded a custom certificate](/ssl/edge-certificates/custom-certificates/) or purchased [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) to protect your domain. - + To disable Universal SSL in the dashboard: @@ -44,7 +44,7 @@ To disable Universal SSL in the dashboard: 5. Read the warnings in the **Acknowledgement**. 6. Select **I Understand** and select **Confirm**. - + To disable Universal SSL with the Cloudflare API, send a [`PATCH`](/api/operations/universal-ssl-settings-for-a-zone-edit-universal-ssl-settings) request and include the `"enabled": false` parameter. @@ -56,7 +56,7 @@ Even with Universal SSL disabled, some features such as [AMP Real URL](/speed/op ## Re-enable Universal SSL - + To re-enable Universal SSL in the dashboard: @@ -65,7 +65,7 @@ To re-enable Universal SSL in the dashboard: 3. Go to **SSL/TLS** > **Edge Certificates**. 4. For **Disable Universal SSL**, select **Enable Universal SSL**. - + To re-enable Universal SSL with the Cloudflare API, send a [`PATCH`](/api/operations/universal-ssl-settings-for-a-zone-edit-universal-ssl-settings) request and include the `"enabled": true` parameter. diff --git a/src/content/docs/ssl/keyless-ssl/configuration/public-dns.mdx b/src/content/docs/ssl/keyless-ssl/configuration/public-dns.mdx index 0c38f5ed5a2487..ee77c024d1a67a 100644 --- a/src/content/docs/ssl/keyless-ssl/configuration/public-dns.mdx +++ b/src/content/docs/ssl/keyless-ssl/configuration/public-dns.mdx @@ -41,7 +41,7 @@ As a security measure, you should hide the hostname of your key server. - + To create a Keyless certificate in the dashboard: @@ -58,7 +58,7 @@ To create a Keyless certificate in the dashboard: | SSL Certificate | The valid X509v3 SSL certificate (in PEM form) for which you hold the private key. | (PEM bytes) | | Bundle method | This should almost always be **Compatible**. Refer to [Uploading Custom Certificates](/ssl/edge-certificates/custom-certificates/uploading/) for more details. | Compatible | - + To create a Keyless certificate with the API, send a [`POST`](/api/operations/keyless-ssl-for-a-zone-create-keyless-ssl-configuration) request. diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/flexible.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/flexible.mdx index 6fb49ada3bb871..9267beb590f713 100644 --- a/src/content/docs/ssl/origin-configuration/ssl-modes/flexible.mdx +++ b/src/content/docs/ssl/origin-configuration/ssl-modes/flexible.mdx @@ -32,11 +32,11 @@ Choose this option when you cannot set up an SSL certificate on your origin or y ### Process - + - + diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/full-strict.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/full-strict.mdx index 92d4e17343e37c..ddf26e3ae343b3 100644 --- a/src/content/docs/ssl/origin-configuration/ssl-modes/full-strict.mdx +++ b/src/content/docs/ssl/origin-configuration/ssl-modes/full-strict.mdx @@ -51,11 +51,11 @@ Otherwise, your visitors may experience a [526 error](/support/troubleshooting/c ### Process - + - + diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx index 85c583df35222b..546ae9fe70f8a8 100644 --- a/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx +++ b/src/content/docs/ssl/origin-configuration/ssl-modes/full.mdx @@ -42,11 +42,11 @@ Before enabling **Full** mode, make sure your origin allows HTTPS connections on ### Process - + - + diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx index 3c3b16955796c3..7e06cf4a18e711 100644 --- a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx +++ b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx @@ -32,11 +32,11 @@ If you are not sure which encryption mode to use, enable the [SSL/TLS Recommende ## Update your encryption mode - + - + diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/off.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/off.mdx index 1a8b2c313bf3a2..61839eaf959fc1 100644 --- a/src/content/docs/ssl/origin-configuration/ssl-modes/off.mdx +++ b/src/content/docs/ssl/origin-configuration/ssl-modes/off.mdx @@ -26,11 +26,11 @@ Cloudflare does not recommend setting your encryption mode to **Off**. ## Required setup - + - + diff --git a/src/content/docs/ssl/origin-configuration/ssl-tls-recommender.mdx b/src/content/docs/ssl/origin-configuration/ssl-tls-recommender.mdx index 08d3d75e0c3bd7..f6b93822ba213d 100644 --- a/src/content/docs/ssl/origin-configuration/ssl-tls-recommender.mdx +++ b/src/content/docs/ssl/origin-configuration/ssl-tls-recommender.mdx @@ -30,7 +30,7 @@ For more background, refer to the [introductory blog post](https://blog.cloudfla Then, you can enable the SSL/TLS recommender. - + To enable SSL/TLS recommendations in the dashboard: @@ -38,7 +38,7 @@ To enable SSL/TLS recommendations in the dashboard: 2. Go to **SSL/TLS**. 3. For **SSL/TLS Recommender**, switch the toggle to **On**. - + To adjust your SSL/TLS Recommender enrollment with the API, send a [`PATCH`](/api/operations/ssl/-tls-mode-recommendation-ssl/-tls-recommendation) request with the `enabled` parameter set to your desired setting (`true` or `false`). diff --git a/src/content/docs/ssl/reference/migration-guides/digicert-update/advanced-certificates.mdx b/src/content/docs/ssl/reference/migration-guides/digicert-update/advanced-certificates.mdx index 2191158764d4e2..715feb4986ad46 100644 --- a/src/content/docs/ssl/reference/migration-guides/digicert-update/advanced-certificates.mdx +++ b/src/content/docs/ssl/reference/migration-guides/digicert-update/advanced-certificates.mdx @@ -131,13 +131,13 @@ Notifications can be sent to an email address or a webhook. - + - + diff --git a/src/content/docs/ssl/reference/migration-guides/digicert-update/custom-hostname-certificates.mdx b/src/content/docs/ssl/reference/migration-guides/digicert-update/custom-hostname-certificates.mdx index 39a7b5282b362b..a403999bfcee9c 100644 --- a/src/content/docs/ssl/reference/migration-guides/digicert-update/custom-hostname-certificates.mdx +++ b/src/content/docs/ssl/reference/migration-guides/digicert-update/custom-hostname-certificates.mdx @@ -120,13 +120,13 @@ If the custom hostname is not proxying traffic through Cloudflare, then the cust
- + - + diff --git a/src/content/docs/tenant/get-started/index.mdx b/src/content/docs/tenant/get-started/index.mdx index bf986d9c7a73f1..c9ce4da647e924 100644 --- a/src/content/docs/tenant/get-started/index.mdx +++ b/src/content/docs/tenant/get-started/index.mdx @@ -28,11 +28,11 @@ For more details on using the Cloudflare API, refer to our [API overview](/funda - + - + diff --git a/src/content/docs/tenant/how-to/manage-accounts.mdx b/src/content/docs/tenant/how-to/manage-accounts.mdx index d083a051122a51..2514a5b4357bdf 100644 --- a/src/content/docs/tenant/how-to/manage-accounts.mdx +++ b/src/content/docs/tenant/how-to/manage-accounts.mdx @@ -14,11 +14,11 @@ import { Render, TabItem, Tabs } from "~/components" - + - + @@ -28,14 +28,14 @@ import { Render, TabItem, Tabs } from "~/components" When you create an account with the Tenant API, your Cloudflare user owns that account from creation, ongoing management, and finally deletion. - + To view any accounts owned by your tenant using the dashboard: 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com). 2. Go to **Tenants** > **Managed Accounts**. - + To fetch any accounts owned by your tenant using the API, send a [`GET`](/api/operations/accounts-list-accounts) request to the `/accounts` endpoint. diff --git a/src/content/docs/waf/about/content-scanning/get-started.mdx b/src/content/docs/waf/about/content-scanning/get-started.mdx index 9b3e2d45987caa..9a859d1e5818e4 100644 --- a/src/content/docs/waf/about/content-scanning/get-started.mdx +++ b/src/content/docs/waf/about/content-scanning/get-started.mdx @@ -18,13 +18,13 @@ WAF content scanning is available to customers on an Enterprise plan with a paid ## 1. Enable WAF content scanning - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain. 2. Go to **Security** > **Settings**. 3. Under **Incoming traffic detections**, turn on **Malicious uploads**. - + Enable the feature using a `POST` request similar to the following: @@ -103,7 +103,7 @@ For additional examples, refer to [Example rules](/waf/about/content-scanning/ex To check uploaded content in a way that is not covered by the default configuration, add a [custom scan expression](/waf/about/content-scanning/#custom-scan-expressions). - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain. @@ -121,7 +121,7 @@ To check uploaded content in a way that is not covered by the default configurat 6. Select **Save**. - + Use a `POST` request similar to the following: diff --git a/src/content/docs/waf/custom-rules/skip/index.mdx b/src/content/docs/waf/custom-rules/skip/index.mdx index 5b83658f5b522c..1a98a265644901 100644 --- a/src/content/docs/waf/custom-rules/skip/index.mdx +++ b/src/content/docs/waf/custom-rules/skip/index.mdx @@ -15,7 +15,7 @@ Use the *Skip* action in a custom rule to skip one or more security features. A For more information on the available options, refer to [Available skip options](/waf/custom-rules/skip/options/). - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain. @@ -33,7 +33,7 @@ For more information on the available options, refer to [Available skip options] 7. Save your changes. - + Use the [Rulesets API](/ruleset-engine/rulesets-api/) to configure custom rules via API. diff --git a/src/content/docs/waf/tools/ip-access-rules/create.mdx b/src/content/docs/waf/tools/ip-access-rules/create.mdx index d4d5910b9176fb..5c2806468b7451 100644 --- a/src/content/docs/waf/tools/ip-access-rules/create.mdx +++ b/src/content/docs/waf/tools/ip-access-rules/create.mdx @@ -11,7 +11,7 @@ head: import { TabItem, Tabs } from "~/components" - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain. @@ -26,7 +26,7 @@ import { TabItem, Tabs } from "~/components" 4. Select **Add**. - + Use the Cloudflare API to programmatically create IP Access rules. For more information, refer to [Get IP Access rules](/api/operations/ip-access-rules-for-a-user-list-ip-access-rules). diff --git a/src/content/docs/waf/tools/replace-insecure-js-libraries.mdx b/src/content/docs/waf/tools/replace-insecure-js-libraries.mdx index 47d8acfe05b43c..9e43dd01e47363 100644 --- a/src/content/docs/waf/tools/replace-insecure-js-libraries.mdx +++ b/src/content/docs/waf/tools/replace-insecure-js-libraries.mdx @@ -36,13 +36,13 @@ The feature is available in all Cloudflare plans, and is turned on by default on ## Configure - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and zone. 2. Go to **Security** > **Settings**. 3. For **Replace insecure JavaScript libraries**, switch the toggle to **On** or **Off**. - + Issue a `PATCH` request similar to the following: diff --git a/src/content/docs/waf/tools/scrape-shield/email-address-obfuscation.mdx b/src/content/docs/waf/tools/scrape-shield/email-address-obfuscation.mdx index a20ba75cb7d70e..5504d269d9fbf1 100644 --- a/src/content/docs/waf/tools/scrape-shield/email-address-obfuscation.mdx +++ b/src/content/docs/waf/tools/scrape-shield/email-address-obfuscation.mdx @@ -21,7 +21,7 @@ Web administrators have come up with clever ways to protect against this by writ Cloudflare enables email address obfuscation automatically when you sign up. - + To disable **Email Address Obfuscation** in the dashboard: @@ -30,7 +30,7 @@ To disable **Email Address Obfuscation** in the dashboard: 3. Go to **Scrape Shield**. 4. For **Email Address Obfuscation**, switch the toggle to **Off**. - + To disable **Email Address Obfuscation** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `email_obfuscation` as the setting name in the URI path, and the `value` parameter set to `"off"`. diff --git a/src/content/docs/waf/tools/scrape-shield/hotlink-protection.mdx b/src/content/docs/waf/tools/scrape-shield/hotlink-protection.mdx index 456f0b5d196659..c6602579a9b5b8 100644 --- a/src/content/docs/waf/tools/scrape-shield/hotlink-protection.mdx +++ b/src/content/docs/waf/tools/scrape-shield/hotlink-protection.mdx @@ -30,7 +30,7 @@ Hotlink protection has no impact on crawling, but it will prevent the images fro ## Enable Hotlink Protection - + To enable **Hotlink Protection** in the dashboard: @@ -39,7 +39,7 @@ To enable **Hotlink Protection** in the dashboard: 3. Go to **Scrape Shield**. 4. For **Hotlink Protection**, switch the toggle to **On**. - + To enable **Hotlink Protection** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `hotlink_protection` as the setting name in the URI path, and the `value` parameter set to `"on"`. diff --git a/src/content/docs/waf/tools/user-agent-blocking.mdx b/src/content/docs/waf/tools/user-agent-blocking.mdx index dcf07d6c4e0966..fa13557b2af8ce 100644 --- a/src/content/docs/waf/tools/user-agent-blocking.mdx +++ b/src/content/docs/waf/tools/user-agent-blocking.mdx @@ -31,7 +31,7 @@ Cloudflare User Agent Blocking is available on all plans. The number of availabl ## Create a User Agent Blocking rule - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain. @@ -47,7 +47,7 @@ Cloudflare User Agent Blocking is available on all plans. The number of availabl 7. Select **Save and Deploy blocking rule**. - + Issue a `POST` request for the [Create a User Agent Blocking rule](/api/operations/user-agent-blocking-rules-create-a-user-agent-blocking-rule) operation. diff --git a/src/content/docs/waf/tools/zone-lockdown.mdx b/src/content/docs/waf/tools/zone-lockdown.mdx index ffce32fabb2a1d..5e372b334eb494 100644 --- a/src/content/docs/waf/tools/zone-lockdown.mdx +++ b/src/content/docs/waf/tools/zone-lockdown.mdx @@ -34,7 +34,7 @@ Cloudflare Zone Lockdown is available on paid plans. The number of available Zon ## Create a Zone Lockdown rule - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain. @@ -52,7 +52,7 @@ Cloudflare Zone Lockdown is available on paid plans. The number of available Zon 8. Select **Save and Deploy lockdown rule**. - + Issue a `POST` request for the [Create a Zone Lockdown rule](/api/operations/zone-lockdown-create-a-zone-lockdown-rule) operation. diff --git a/src/content/docs/waiting-room/how-to/create-waiting-room.mdx b/src/content/docs/waiting-room/how-to/create-waiting-room.mdx index 6d36bbc85998e3..070ff8b96f0015 100644 --- a/src/content/docs/waiting-room/how-to/create-waiting-room.mdx +++ b/src/content/docs/waiting-room/how-to/create-waiting-room.mdx @@ -17,7 +17,7 @@ You can create a waiting room from the dashboard or via API. For additional context on creating a waiting room, refer to [Get started](/waiting-room/get-started/). ::: - + 1. Within your application, go to **Traffic** > **Waiting Room**. 2. Select **Create**. @@ -29,7 +29,7 @@ For additional context on creating a waiting room, refer to [Get started](/waiti 8. Review your settings before saving. If you customized your waiting room, make sure to [preview the result](/waiting-room/how-to/customize-waiting-room/#preview-waiting-room). 9. Select **Save**. Your new waiting room will be enabled by default. - + To create a Waiting Room using the API, send a [`POST` request](/api/operations/waiting-room-create-waiting-room) to the `/zones/{zone_identifier}/waiting_rooms` endpoint: diff --git a/src/content/docs/web3/how-to/manage-gateways.mdx b/src/content/docs/web3/how-to/manage-gateways.mdx index 977204e397901f..c6def243471081 100644 --- a/src/content/docs/web3/how-to/manage-gateways.mdx +++ b/src/content/docs/web3/how-to/manage-gateways.mdx @@ -12,11 +12,11 @@ A Cloudflare Web3 gateway provides HTTP-accessible interfaces to various Web3 ne ## Create a gateway - + - + @@ -32,7 +32,7 @@ Once you have [created a gateway](#create-a-gateway), you can only edit the **Ga If you need to edit other fields, [delete the gateway](#delete-a-gateway) and create a new one. - + To edit a gateway using the dashboard: @@ -43,7 +43,7 @@ To edit a gateway using the dashboard: 5. Update the **Gateway Description** and — if editing an **IPFS** gateway — the value for the [DNSLink](/web3/ipfs-gateway/concepts/dnslink/). 6. Click **Reapply**. - + To edit specific settings for a gateway, use a [`PATCH`](/api/operations/web3-hostname-edit-web3-hostname) request. @@ -55,7 +55,7 @@ To edit specific settings for a gateway, use a [`PATCH`](/api/operations/web3-ho When your gateway is stuck in an **Error** [status](/web3/reference/gateway-status/), you should try refreshing the gateway, which attempts to re-create the associated DNS records for the hostname. - + To refresh a gateway using the dashboard: @@ -64,7 +64,7 @@ To refresh a gateway using the dashboard: 3. Go to **Web3**. 4. On a gateway, click the dropdown then **Refresh**. - + To refresh a gateway using the API, send a [`PATCH`](/api/operations/web3-hostname-edit-web3-hostname) request with an empty request body. @@ -82,7 +82,7 @@ You have the ability to block access to one or more: * IPFS content paths (`/ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme`) * IPNS content paths (`/ipns/example.com`) - + To add an item to the blocklist using the dashboard: @@ -104,7 +104,7 @@ To add an item to the blocklist using the dashboard: 7. Click **Add**. - + To add a blocklist item using the API, send a [`POST`](/api/operations/web3-hostname-create-ipfs-universal-path-gateway-content-list-entry) request. @@ -116,7 +116,7 @@ To add a blocklist item using the API, send a [`POST`](/api/operations/web3-host When you delete a gateway, Cloudflare will automatically remove all associated hostname DNS records. This action will impact your traffic and cannot be undone. - + To delete a gateway using the dashboard: @@ -126,7 +126,7 @@ To delete a gateway using the dashboard: 4. On a specific gateway, click the dropdown then **Remove**. 5. Click **Delete hostname**. - + To delete a gateway using the API, send a [`DELETE`](/api/operations/web3-hostname-delete-web3-hostname) request. diff --git a/src/content/docs/workers/configuration/environment-variables.mdx b/src/content/docs/workers/configuration/environment-variables.mdx index ff89d8214824fe..2f13a97f39e9f5 100644 --- a/src/content/docs/workers/configuration/environment-variables.mdx +++ b/src/content/docs/workers/configuration/environment-variables.mdx @@ -22,7 +22,7 @@ Text and JSON values are defined via the `[vars]` configuration in your `wrangle Refer to the following example on how to access the `API_HOST` environment variable in your Worker code: - + ```js export default { @@ -32,7 +32,7 @@ export default { } ``` - + ```ts export interface Env { diff --git a/src/content/docs/workers/configuration/sites/start-from-existing.mdx b/src/content/docs/workers/configuration/sites/start-from-existing.mdx index edde1c8ce4c687..fc746470d697a4 100644 --- a/src/content/docs/workers/configuration/sites/start-from-existing.mdx +++ b/src/content/docs/workers/configuration/sites/start-from-existing.mdx @@ -57,7 +57,7 @@ To deploy a pre-existing static site project, start with a pre-generated site. W 4. Replace the contents of `src/index.ts` with the following code snippet: - + ```js import { getAssetFromKV } from '@cloudflare/kv-asset-handler'; @@ -89,7 +89,7 @@ export default { }; ``` - + ```js import { getAssetFromKV } from "@cloudflare/kv-asset-handler"; diff --git a/src/content/docs/workers/configuration/sites/start-from-worker.mdx b/src/content/docs/workers/configuration/sites/start-from-worker.mdx index faba0664545e03..818eb038f81eec 100644 --- a/src/content/docs/workers/configuration/sites/start-from-worker.mdx +++ b/src/content/docs/workers/configuration/sites/start-from-worker.mdx @@ -33,7 +33,7 @@ If you have a pre-existing Worker project, you can use Workers Sites to serve st 4. Import the `getAssetFromKV()` function into your Worker entry point and use it to respond with static assets. - + ```js import { getAssetFromKV } from '@cloudflare/kv-asset-handler'; @@ -65,7 +65,7 @@ export default { }; ``` - + ```js import { getAssetFromKV } from "@cloudflare/kv-asset-handler"; diff --git a/src/content/docs/workers/examples/103-early-hints.mdx b/src/content/docs/workers/examples/103-early-hints.mdx index f9262b253c3d10..63df947a8333ff 100644 --- a/src/content/docs/workers/examples/103-early-hints.mdx +++ b/src/content/docs/workers/examples/103-early-hints.mdx @@ -28,7 +28,7 @@ To ensure Early Hints are enabled on your zone: You can return `Link` headers from a Worker running on your zone to speed up your page load times. - + ```js const CSS = "body { color: red; }"; @@ -68,7 +68,7 @@ export default { }; ``` - + ```js const CSS = "body { color: red; }"; @@ -108,7 +108,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import re diff --git a/src/content/docs/workers/examples/ab-testing.mdx b/src/content/docs/workers/examples/ab-testing.mdx index bdb27e437249e7..cda7101d5ae58c 100644 --- a/src/content/docs/workers/examples/ab-testing.mdx +++ b/src/content/docs/workers/examples/ab-testing.mdx @@ -19,7 +19,7 @@ description: Set up an A/B test by controlling what response is served based on import { TabItem, Tabs } from "~/components" - + ```js const NAME = "myExampleWorkersABTest"; @@ -59,7 +59,7 @@ export default { }; ``` - + ```ts const NAME = "myExampleWorkersABTest"; @@ -96,7 +96,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import random diff --git a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx index 3a4853fe38a708..4a883f6ce67609 100644 --- a/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx +++ b/src/content/docs/workers/examples/accessing-the-cloudflare-object.mdx @@ -19,7 +19,7 @@ description: Access custom Cloudflare properties and control how Cloudflare import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -38,7 +38,7 @@ export default { }; ``` - + ```ts export default { @@ -57,7 +57,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import json diff --git a/src/content/docs/workers/examples/aggregate-requests.mdx b/src/content/docs/workers/examples/aggregate-requests.mdx index 167d48eb2f5db5..b8c16588d67add 100644 --- a/src/content/docs/workers/examples/aggregate-requests.mdx +++ b/src/content/docs/workers/examples/aggregate-requests.mdx @@ -17,7 +17,7 @@ description: Send two GET request to two urls and aggregates the responses into import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -38,7 +38,7 @@ export default { }; ``` - + ```ts export default { @@ -57,7 +57,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch, Headers, JSON, Promise diff --git a/src/content/docs/workers/examples/alter-headers.mdx b/src/content/docs/workers/examples/alter-headers.mdx index f113a214e55fca..91a5952d45cc29 100644 --- a/src/content/docs/workers/examples/alter-headers.mdx +++ b/src/content/docs/workers/examples/alter-headers.mdx @@ -22,7 +22,7 @@ description: Example of how to add, change, or delete headers sent in a request import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -50,7 +50,7 @@ export default { }; ``` - + ```ts export default { @@ -78,7 +78,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch diff --git a/src/content/docs/workers/examples/auth-with-headers.mdx b/src/content/docs/workers/examples/auth-with-headers.mdx index e6024dfdd62aed..67fccae5d88a2a 100644 --- a/src/content/docs/workers/examples/auth-with-headers.mdx +++ b/src/content/docs/workers/examples/auth-with-headers.mdx @@ -25,7 +25,7 @@ import { TabItem, Tabs } from "~/components" The example code contains a generic header key and value of `X-Custom-PSK` and `mypresharedkey`. To best protect your resources, change the header key and value in the Workers editor before saving your code. ::: - + ```js export default { @@ -51,7 +51,7 @@ export default { }; ``` - + ```ts export default { @@ -77,7 +77,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch diff --git a/src/content/docs/workers/examples/basic-auth.mdx b/src/content/docs/workers/examples/basic-auth.mdx index 02179599ba021e..a62403a3a3774d 100644 --- a/src/content/docs/workers/examples/basic-auth.mdx +++ b/src/content/docs/workers/examples/basic-auth.mdx @@ -34,7 +34,7 @@ This code is provided as a sample, and is not suitable for production use. Basic ::: - + ```js /** @@ -151,7 +151,7 @@ export default { }; ``` - + ```ts /** diff --git a/src/content/docs/workers/examples/block-on-tls.mdx b/src/content/docs/workers/examples/block-on-tls.mdx index 6b61f713b985ce..05cc9c06c8ae9c 100644 --- a/src/content/docs/workers/examples/block-on-tls.mdx +++ b/src/content/docs/workers/examples/block-on-tls.mdx @@ -18,7 +18,7 @@ description: Inspects the incoming request's TLS version and blocks if under TLS import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -44,7 +44,7 @@ export default { }; ``` - + ```ts export default { @@ -70,7 +70,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch diff --git a/src/content/docs/workers/examples/bulk-origin-proxy.mdx b/src/content/docs/workers/examples/bulk-origin-proxy.mdx index 544f4a5465fa15..d597f1918b0567 100644 --- a/src/content/docs/workers/examples/bulk-origin-proxy.mdx +++ b/src/content/docs/workers/examples/bulk-origin-proxy.mdx @@ -17,7 +17,7 @@ description: Resolve requests to your domain to a set of proxy third-party origi import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -46,7 +46,7 @@ export default { }; ``` - + ```ts export default { @@ -75,7 +75,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import fetch, URL diff --git a/src/content/docs/workers/examples/bulk-redirects.mdx b/src/content/docs/workers/examples/bulk-redirects.mdx index 63810933273df6..4f7f1f3b64efd2 100644 --- a/src/content/docs/workers/examples/bulk-redirects.mdx +++ b/src/content/docs/workers/examples/bulk-redirects.mdx @@ -20,7 +20,7 @@ description: Redirect requests to certain URLs based on a mapped object to the import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -47,7 +47,7 @@ export default { }; ``` - + ```ts export default { @@ -74,7 +74,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch, URL diff --git a/src/content/docs/workers/examples/cache-api.mdx b/src/content/docs/workers/examples/cache-api.mdx index 84086d15247515..342f6325a0f457 100644 --- a/src/content/docs/workers/examples/cache-api.mdx +++ b/src/content/docs/workers/examples/cache-api.mdx @@ -18,7 +18,7 @@ description: Use the Cache API to store responses in Cloudflare's cache. import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -58,7 +58,7 @@ export default { }; ``` - + ```ts interface Env {} @@ -99,7 +99,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from pyodide.ffi import create_proxy diff --git a/src/content/docs/workers/examples/cache-post-request.mdx b/src/content/docs/workers/examples/cache-post-request.mdx index 398682bf87484c..f47c4a2b99d68d 100644 --- a/src/content/docs/workers/examples/cache-post-request.mdx +++ b/src/content/docs/workers/examples/cache-post-request.mdx @@ -18,7 +18,7 @@ description: Cache POST requests using the Cache API. import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -65,7 +65,7 @@ export default { }; ``` - + ```ts interface Env {} @@ -113,7 +113,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import hashlib diff --git a/src/content/docs/workers/examples/cache-tags.mdx b/src/content/docs/workers/examples/cache-tags.mdx index 7fe56fa7c3bafb..cb712e877fc1a0 100644 --- a/src/content/docs/workers/examples/cache-tags.mdx +++ b/src/content/docs/workers/examples/cache-tags.mdx @@ -17,7 +17,7 @@ description: Send Additional Cache Tags using Workers import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -61,7 +61,7 @@ export default { }; ``` - + ```ts export default { @@ -105,7 +105,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from pyodide.ffi import to_js as _to_js diff --git a/src/content/docs/workers/examples/cache-using-fetch.mdx b/src/content/docs/workers/examples/cache-using-fetch.mdx index a7d7d5498ae230..ed4e1e2f280b67 100644 --- a/src/content/docs/workers/examples/cache-using-fetch.mdx +++ b/src/content/docs/workers/examples/cache-using-fetch.mdx @@ -21,7 +21,7 @@ description: Determine how to cache a resource by setting TTLs, custom cache import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -49,7 +49,7 @@ export default { }; ``` - + ```ts export default { @@ -77,7 +77,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from pyodide.ffi import to_js as _to_js @@ -114,7 +114,7 @@ async def on_fetch(request): return response ``` - + ```rs use worker::*; @@ -191,7 +191,7 @@ Normally, Cloudflare computes the cache key for a request based on the request's - + ```js export default { @@ -212,7 +212,7 @@ export default { }; ``` - + ```ts export default { @@ -263,7 +263,7 @@ The following example demonstrates how you might use this to cache requests for - + ```js title="index.js" export default { @@ -317,7 +317,7 @@ export default { } ``` - + ```js title="index.js" addEventListener('fetch', event => { diff --git a/src/content/docs/workers/examples/conditional-response.mdx b/src/content/docs/workers/examples/conditional-response.mdx index d1ef98689fa31f..a0fd338a1e2798 100644 --- a/src/content/docs/workers/examples/conditional-response.mdx +++ b/src/content/docs/workers/examples/conditional-response.mdx @@ -19,7 +19,7 @@ description: Return a response based on the incoming request's URL, HTTP method, import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -68,7 +68,7 @@ export default { }; ``` - + ```ts export default { @@ -117,7 +117,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import re diff --git a/src/content/docs/workers/examples/cors-header-proxy.mdx b/src/content/docs/workers/examples/cors-header-proxy.mdx index e8c428fa1c7892..7c6c40fb8d289f 100644 --- a/src/content/docs/workers/examples/cors-header-proxy.mdx +++ b/src/content/docs/workers/examples/cors-header-proxy.mdx @@ -18,7 +18,7 @@ description: Add the necessary CORS headers to a third party API response. import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -173,7 +173,7 @@ export default { }; ``` - + ```ts export default { @@ -328,7 +328,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from pyodide.ffi import to_js as _to_js diff --git a/src/content/docs/workers/examples/country-code-redirect.mdx b/src/content/docs/workers/examples/country-code-redirect.mdx index c5cb4be33b4712..24ac4a93062fcb 100644 --- a/src/content/docs/workers/examples/country-code-redirect.mdx +++ b/src/content/docs/workers/examples/country-code-redirect.mdx @@ -20,7 +20,7 @@ description: Redirect a response based on the country code in the header of a vi import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -50,7 +50,7 @@ export default { }; ``` - + ```ts export default { @@ -78,7 +78,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch diff --git a/src/content/docs/workers/examples/cron-trigger.mdx b/src/content/docs/workers/examples/cron-trigger.mdx index 616b892ea74621..84d2c51ee67628 100644 --- a/src/content/docs/workers/examples/cron-trigger.mdx +++ b/src/content/docs/workers/examples/cron-trigger.mdx @@ -16,7 +16,7 @@ description: Set a Cron Trigger for your Worker. import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -26,7 +26,7 @@ export default { }; ``` - + ```ts interface Env {} diff --git a/src/content/docs/workers/examples/data-loss-prevention.mdx b/src/content/docs/workers/examples/data-loss-prevention.mdx index 11d548511a72f6..d3c26ca141a177 100644 --- a/src/content/docs/workers/examples/data-loss-prevention.mdx +++ b/src/content/docs/workers/examples/data-loss-prevention.mdx @@ -19,7 +19,7 @@ description: Protect sensitive data to prevent data loss, and send alerts to a import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -92,7 +92,7 @@ export default { }; ``` - + ```ts export default { @@ -165,7 +165,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import re diff --git a/src/content/docs/workers/examples/debugging-logs.mdx b/src/content/docs/workers/examples/debugging-logs.mdx index 64e1802c0825db..4164834b60e797 100644 --- a/src/content/docs/workers/examples/debugging-logs.mdx +++ b/src/content/docs/workers/examples/debugging-logs.mdx @@ -17,7 +17,7 @@ description: Send debugging information in an errored response to a logging serv import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -62,7 +62,7 @@ export default { }; ``` - + ```ts interface Env {} @@ -108,7 +108,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import json diff --git a/src/content/docs/workers/examples/extract-cookie-value.mdx b/src/content/docs/workers/examples/extract-cookie-value.mdx index 54f3c80b396f1a..51d46d210369a7 100644 --- a/src/content/docs/workers/examples/extract-cookie-value.mdx +++ b/src/content/docs/workers/examples/extract-cookie-value.mdx @@ -19,7 +19,7 @@ description: Given the cookie name, get the value of a cookie. You can also use import { TabItem, Tabs } from "~/components" - + ```js import { parse } from "cookie"; @@ -37,7 +37,7 @@ export default { }; ``` - + ```ts import { parse } from "cookie"; @@ -55,7 +55,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from http.cookies import SimpleCookie diff --git a/src/content/docs/workers/examples/fetch-html.mdx b/src/content/docs/workers/examples/fetch-html.mdx index a5de2719571ce6..27b3895db89d82 100644 --- a/src/content/docs/workers/examples/fetch-html.mdx +++ b/src/content/docs/workers/examples/fetch-html.mdx @@ -20,11 +20,11 @@ description: Send a request to a remote server, read HTML from the response, and import { Render, TabItem, Tabs } from "~/components" - + - + ```ts export default { @@ -39,7 +39,7 @@ export default { }; ``` - + ```py from js import fetch diff --git a/src/content/docs/workers/examples/fetch-json.mdx b/src/content/docs/workers/examples/fetch-json.mdx index 22988c10b0c02c..09a812e81b6441 100644 --- a/src/content/docs/workers/examples/fetch-json.mdx +++ b/src/content/docs/workers/examples/fetch-json.mdx @@ -19,7 +19,7 @@ description: Send a GET request and read in JSON from the response. Use to fetch import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -45,7 +45,7 @@ export default { }; ``` - + ```ts interface Env {} @@ -72,7 +72,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch, Headers, JSON diff --git a/src/content/docs/workers/examples/geolocation-app-weather.mdx b/src/content/docs/workers/examples/geolocation-app-weather.mdx index 3f092f15f3b92d..1c5acd4d1d8ecd 100644 --- a/src/content/docs/workers/examples/geolocation-app-weather.mdx +++ b/src/content/docs/workers/examples/geolocation-app-weather.mdx @@ -17,7 +17,7 @@ description: Fetch weather data from an API using the user's geolocation data. import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -69,7 +69,7 @@ export default { }; ``` - + ```ts export default { @@ -121,7 +121,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, Headers, fetch diff --git a/src/content/docs/workers/examples/geolocation-custom-styling.mdx b/src/content/docs/workers/examples/geolocation-custom-styling.mdx index 954fac56a6c763..017aa31d654756 100644 --- a/src/content/docs/workers/examples/geolocation-custom-styling.mdx +++ b/src/content/docs/workers/examples/geolocation-custom-styling.mdx @@ -16,7 +16,7 @@ description: Personalize website styling based on localized user time. import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -186,7 +186,7 @@ export default { }; ``` - + ```ts export default { diff --git a/src/content/docs/workers/examples/geolocation-hello-world.mdx b/src/content/docs/workers/examples/geolocation-hello-world.mdx index f5e8220beb5e4f..c802b73d9e592c 100644 --- a/src/content/docs/workers/examples/geolocation-hello-world.mdx +++ b/src/content/docs/workers/examples/geolocation-hello-world.mdx @@ -19,7 +19,7 @@ description: Get all geolocation data fields and display them in HTML. import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -60,7 +60,7 @@ export default { }; ``` - + ```ts export default { @@ -101,7 +101,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, Headers diff --git a/src/content/docs/workers/examples/hot-link-protection.mdx b/src/content/docs/workers/examples/hot-link-protection.mdx index fc1c64d3c44019..62d84f4f814f25 100644 --- a/src/content/docs/workers/examples/hot-link-protection.mdx +++ b/src/content/docs/workers/examples/hot-link-protection.mdx @@ -20,7 +20,7 @@ description: Block other websites from linking to your content. This is useful import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -50,7 +50,7 @@ export default { }; ``` - + ```ts export default { @@ -80,7 +80,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, URL, fetch diff --git a/src/content/docs/workers/examples/images-workers.mdx b/src/content/docs/workers/examples/images-workers.mdx index deb1b2a4108230..bfb69f32f6aab3 100644 --- a/src/content/docs/workers/examples/images-workers.mdx +++ b/src/content/docs/workers/examples/images-workers.mdx @@ -26,7 +26,7 @@ To serve images from a custom domain: 3. Select **Create application** > **Workers** > **Create Worker** and create your Worker. 4. In your Worker, select **Quick edit** and paste the following code. - + ```js export default { @@ -44,7 +44,7 @@ export default { }; ``` - + ```ts export default { @@ -62,7 +62,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import URL, fetch diff --git a/src/content/docs/workers/examples/logging-headers.mdx b/src/content/docs/workers/examples/logging-headers.mdx index 33b6743b051fc0..9f69b3898c0b45 100644 --- a/src/content/docs/workers/examples/logging-headers.mdx +++ b/src/content/docs/workers/examples/logging-headers.mdx @@ -20,7 +20,7 @@ description: Examine the contents of a Headers object by logging to console with import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -31,7 +31,7 @@ export default { }; ``` - + ```ts export default { @@ -42,7 +42,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response diff --git a/src/content/docs/workers/examples/modify-request-property.mdx b/src/content/docs/workers/examples/modify-request-property.mdx index 0617b43948f188..d56926d9257da9 100644 --- a/src/content/docs/workers/examples/modify-request-property.mdx +++ b/src/content/docs/workers/examples/modify-request-property.mdx @@ -20,7 +20,7 @@ description: Create a modified request with edited properties based off of an import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -79,7 +79,7 @@ export default { }; ``` - + ```ts export default { @@ -138,7 +138,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import json diff --git a/src/content/docs/workers/examples/modify-response.mdx b/src/content/docs/workers/examples/modify-response.mdx index 82d68118c44803..81df2771c8a3af 100644 --- a/src/content/docs/workers/examples/modify-response.mdx +++ b/src/content/docs/workers/examples/modify-response.mdx @@ -20,7 +20,7 @@ description: Fetch and modify response properties which are immutable by import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -70,7 +70,7 @@ export default { }; ``` - + ```ts export default { @@ -120,7 +120,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch, JSON diff --git a/src/content/docs/workers/examples/multiple-cron-triggers.mdx b/src/content/docs/workers/examples/multiple-cron-triggers.mdx index 66b83a477d7469..e0bb82acf70a11 100644 --- a/src/content/docs/workers/examples/multiple-cron-triggers.mdx +++ b/src/content/docs/workers/examples/multiple-cron-triggers.mdx @@ -16,7 +16,7 @@ description: Set multiple Cron Triggers on three different schedules. import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -41,7 +41,7 @@ export default { }; ``` - + ```ts interface Env {} diff --git a/src/content/docs/workers/examples/post-json.mdx b/src/content/docs/workers/examples/post-json.mdx index 100c570aa379b3..3d129bfdd83796 100644 --- a/src/content/docs/workers/examples/post-json.mdx +++ b/src/content/docs/workers/examples/post-json.mdx @@ -17,7 +17,7 @@ description: Send a POST request with JSON data. Use to share data with external import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -69,7 +69,7 @@ export default { }; ``` - + ```ts export default { @@ -121,7 +121,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py import json diff --git a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx index ac9e5c37b9e230..36f546b626f073 100644 --- a/src/content/docs/workers/examples/protect-against-timing-attacks.mdx +++ b/src/content/docs/workers/examples/protect-against-timing-attacks.mdx @@ -29,7 +29,7 @@ Handling of secrets should be taken with care to not introduce timing side chann In order to compare two strings, you must use the [`TextEncoder`](/workers/runtime-apis/encoding/#textencoder) API. - + ```ts interface Environment { @@ -66,7 +66,7 @@ export default { }; ``` - + ```py from js import Response, TextEncoder, crypto diff --git a/src/content/docs/workers/examples/read-post.mdx b/src/content/docs/workers/examples/read-post.mdx index 0d3473b6eed351..30f144d7bf2af2 100644 --- a/src/content/docs/workers/examples/read-post.mdx +++ b/src/content/docs/workers/examples/read-post.mdx @@ -20,7 +20,7 @@ description: Serve an HTML form, then read POST requests. Use also to read JSON import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -80,7 +80,7 @@ export default { }; ``` - + ```ts export default { @@ -140,7 +140,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py @@ -174,7 +174,7 @@ async def on_fetch(request): return Response.new("The request was not POST") ``` - + ```rs use serde::{Deserialize, Serialize}; diff --git a/src/content/docs/workers/examples/redirect.mdx b/src/content/docs/workers/examples/redirect.mdx index eaebdac523cf3c..0090bb97507d7e 100644 --- a/src/content/docs/workers/examples/redirect.mdx +++ b/src/content/docs/workers/examples/redirect.mdx @@ -25,11 +25,11 @@ import { Render, TabItem, Tabs } from "~/components" ## Redirect all requests to one URL - + - + ```ts export default { @@ -41,7 +41,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response @@ -52,7 +52,7 @@ def on_fetch(request): return Response.redirect(destinationURL, statusCode) ``` - + ```rs use worker::*; @@ -70,7 +70,7 @@ async fn fetch(_req: Request, _env: Env, _ctx: Context) -> Result { ## Redirect requests from one domain to another - + ```js export default { @@ -89,7 +89,7 @@ export default { }; ``` - + ```ts export default { @@ -108,7 +108,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, URL @@ -125,7 +125,7 @@ async def on_fetch(request): return Response.redirect(destinationURL, statusCode) ``` - + ```rs use worker::*; diff --git a/src/content/docs/workers/examples/respond-with-another-site.mdx b/src/content/docs/workers/examples/respond-with-another-site.mdx index 979bb908c8e9b8..f15e86d12eb2f1 100644 --- a/src/content/docs/workers/examples/respond-with-another-site.mdx +++ b/src/content/docs/workers/examples/respond-with-another-site.mdx @@ -22,11 +22,11 @@ description: Respond to the Worker request with the response from another import { Render, TabItem, Tabs } from "~/components" - + - + ```ts export default { @@ -46,7 +46,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch, Headers diff --git a/src/content/docs/workers/examples/return-html.mdx b/src/content/docs/workers/examples/return-html.mdx index 0dea6fd9334227..00ee3ec83ebd6d 100644 --- a/src/content/docs/workers/examples/return-html.mdx +++ b/src/content/docs/workers/examples/return-html.mdx @@ -21,11 +21,11 @@ description: Deliver an HTML page from an HTML string directly inside the Worker import { Render, TabItem, Tabs } from "~/components" - + - + ```ts export default { @@ -45,7 +45,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, Headers @@ -61,7 +61,7 @@ def on_fetch(request): return Response.new(html, headers=headers) ``` - + ```rs use worker::*; diff --git a/src/content/docs/workers/examples/return-json.mdx b/src/content/docs/workers/examples/return-json.mdx index 3ac83a54c33d37..f7e8484826dce4 100644 --- a/src/content/docs/workers/examples/return-json.mdx +++ b/src/content/docs/workers/examples/return-json.mdx @@ -24,11 +24,11 @@ description: Return JSON directly from a Worker script, useful for building APIs import { Render, TabItem, Tabs } from "~/components" - + - + ```ts export default { @@ -42,7 +42,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, Headers @@ -54,7 +54,7 @@ def on_fetch(request): return Response.new(data, headers=headers) ``` - + ```rs use serde::{Deserialize, Serialize}; diff --git a/src/content/docs/workers/examples/rewrite-links.mdx b/src/content/docs/workers/examples/rewrite-links.mdx index 8acd42b44c9d68..bed5c9311d99b6 100644 --- a/src/content/docs/workers/examples/rewrite-links.mdx +++ b/src/content/docs/workers/examples/rewrite-links.mdx @@ -19,7 +19,7 @@ description: Rewrite URL links in HTML using the HTMLRewriter. This is useful import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -60,7 +60,7 @@ export default { }; ``` - + ```ts export default { @@ -101,7 +101,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from pyodide.ffi import create_proxy diff --git a/src/content/docs/workers/examples/security-headers.mdx b/src/content/docs/workers/examples/security-headers.mdx index bffe1532b57ab9..f8722175cedcc2 100644 --- a/src/content/docs/workers/examples/security-headers.mdx +++ b/src/content/docs/workers/examples/security-headers.mdx @@ -22,7 +22,7 @@ description: Set common security headers (X-XSS-Protection, X-Frame-Options, import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -110,7 +110,7 @@ export default { }; ``` - + ```ts export default { @@ -198,7 +198,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from js import Response, fetch, Headers diff --git a/src/content/docs/workers/examples/signing-requests.mdx b/src/content/docs/workers/examples/signing-requests.mdx index 31f5e5c315bc58..507b283548f593 100644 --- a/src/content/docs/workers/examples/signing-requests.mdx +++ b/src/content/docs/workers/examples/signing-requests.mdx @@ -35,7 +35,7 @@ The following Worker will: * For all other request URLs, verify the signed URL and allow the request through. - + ```js import { Buffer } from "node:buffer"; @@ -142,7 +142,7 @@ export default { }; ``` - + ```ts import { Buffer } from "node:buffer"; diff --git a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx index 582ff2d31c2765..fecd326c1453ce 100644 --- a/src/content/docs/workers/examples/turnstile-html-rewriter.mdx +++ b/src/content/docs/workers/examples/turnstile-html-rewriter.mdx @@ -19,7 +19,7 @@ description: Inject [Turnstile](/turnstile/) implicitly into HTML elements using import { TabItem, Tabs } from "~/components" - + ```js export default { @@ -53,7 +53,7 @@ export default { } ``` - + ```ts export default { @@ -87,7 +87,7 @@ export default { } satisfies ExportedHandler; ``` - + ```py from pyodide.ffi import create_proxy @@ -126,7 +126,7 @@ async def on_fetch(request, env): This is only half the implementation for Turnstile. The corresponding token that is a result of a widget being rendered also needs to be verified using the [siteverify API](/turnstile/get-started/server-side-validation/). Refer to the example below for one such implementation. ::: - + ```js async function handlePost(request) { diff --git a/src/content/docs/workers/observability/errors.mdx b/src/content/docs/workers/observability/errors.mdx index 61ed4b4b0f77e3..321e299080bd7e 100644 --- a/src/content/docs/workers/observability/errors.mdx +++ b/src/content/docs/workers/observability/errors.mdx @@ -210,7 +210,7 @@ A Worker can make HTTP requests to any HTTP service on the public Internet. You When using an external logging strategy, remember that outstanding asynchronous tasks are canceled as soon as a Worker finishes sending its main response body to the client. To ensure that a logging subrequest completes, pass the request promise to [`event.waitUntil()`](https://developer.mozilla.org/en-US/docs/Web/API/ExtendableEvent/waitUntil). For example: - + ```js export default { @@ -229,7 +229,7 @@ export default { } ``` - + ```js addEventListener("fetch", (event) => { @@ -258,7 +258,7 @@ function postLog(data) { By using [`event.passThroughOnException`](/workers/runtime-apis/context/#passthroughonexception), a Workers application will forward requests to your origin if an exception is thrown during the Worker's execution. This allows you to add logging, tracking, or other features with Workers, without degrading your application's functionality. - + ```js export default { @@ -270,7 +270,7 @@ export default { } ``` - + ```js addEventListener("fetch", (event) => { diff --git a/src/content/docs/workers/observability/logging/real-time-logs.mdx b/src/content/docs/workers/observability/logging/real-time-logs.mdx index 7727653840f24d..c4258af64b2bf6 100644 --- a/src/content/docs/workers/observability/logging/real-time-logs.mdx +++ b/src/content/docs/workers/observability/logging/real-time-logs.mdx @@ -27,7 +27,7 @@ By default a Worker will emit execution logs containing details about the Reques In addition, you can add custom logs throughout your code. Any `console.log` statements within your Worker will be visible in the dashboard or [`wrangler tail`](/workers/wrangler/commands/#tail). The following example demonstrates a custom `console.log` within a Worker request handler. - + ```js export default { @@ -44,7 +44,7 @@ export default { } ``` - + ```js addEventListener("fetch", (event) => { diff --git a/src/content/docs/workers/runtime-apis/bindings/mTLS.mdx b/src/content/docs/workers/runtime-apis/bindings/mTLS.mdx index 5ce7a19b6cb987..99347ff87033e1 100644 --- a/src/content/docs/workers/runtime-apis/bindings/mTLS.mdx +++ b/src/content/docs/workers/runtime-apis/bindings/mTLS.mdx @@ -57,7 +57,7 @@ mTLS certificate bindings present an API similar to [service bindings](/workers/ ### Interface - + ```js export default { @@ -67,7 +67,7 @@ export default { } ``` - + ```js interface Env { diff --git a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx index fc78243d62eb5f..dc9d1c3a371e88 100644 --- a/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx +++ b/src/content/docs/workers/runtime-apis/bindings/rate-limit.mdx @@ -56,7 +56,7 @@ simple = { limit = 100, period = 60 } This binding makes the `MY_RATE_LIMITER` binding available, which provides a `limit()` method: - + ```javascript export default { @@ -73,7 +73,7 @@ export default { } ``` - + ```ts interface Env { diff --git a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx index 91a02a2eebd26b..3dfc723267c28d 100644 --- a/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx +++ b/src/content/docs/workers/runtime-apis/bindings/version-metadata.mdx @@ -31,7 +31,7 @@ binding = "CF_VERSION_METADATA" An example of how to access the version ID and version tag from within a Worker to send events to [Workers Analytics Engine](/analytics/analytics-engine/): - + ```js export default { @@ -47,7 +47,7 @@ export default { }; ``` - + ```ts interface Environment { diff --git a/src/content/docs/workers/runtime-apis/fetch.mdx b/src/content/docs/workers/runtime-apis/fetch.mdx index 0de74024671060..b6ac348f5bc5d2 100644 --- a/src/content/docs/workers/runtime-apis/fetch.mdx +++ b/src/content/docs/workers/runtime-apis/fetch.mdx @@ -29,7 +29,7 @@ Worker-to-Worker `fetch` requests are possible with [Service bindings](/workers/ ## Syntax - + ```js null {3-7} export default { @@ -43,7 +43,7 @@ export default { }; ``` - + ```js null {8} addEventListener('fetch', event => { diff --git a/src/content/docs/workers/runtime-apis/streams/index.mdx b/src/content/docs/workers/runtime-apis/streams/index.mdx index d43452a35974a4..f1cea443428022 100644 --- a/src/content/docs/workers/runtime-apis/streams/index.mdx +++ b/src/content/docs/workers/runtime-apis/streams/index.mdx @@ -33,7 +33,7 @@ By default, Cloudflare Workers is capable of streaming responses using the [Stre The worker can create a `Response` object using a `ReadableStream` as the body. Any data provided through the `ReadableStream` will be streamed to the client as it becomes available. - + ```js export default { @@ -47,7 +47,7 @@ export default { } ``` - + ```js addEventListener('fetch', event => { @@ -67,7 +67,7 @@ async function fetchAndStream(request) { A [`TransformStream`](/workers/runtime-apis/streams/transformstream/) and the [`ReadableStream.pipeTo()`](/workers/runtime-apis/streams/readablestream/#methods) method can be used to modify the response body as it is being streamed: - + ```js export default { @@ -90,7 +90,7 @@ export default { } ``` - + ```js addEventListener('fetch', event => { diff --git a/src/content/docs/workers/runtime-apis/web-crypto.mdx b/src/content/docs/workers/runtime-apis/web-crypto.mdx index da045ae29d3aef..c3ff065c97adb6 100644 --- a/src/content/docs/workers/runtime-apis/web-crypto.mdx +++ b/src/content/docs/workers/runtime-apis/web-crypto.mdx @@ -60,7 +60,7 @@ The Web Crypto API differs significantly from the [Node.js Crypto API](/workers/ ### Usage - + ```js export default { @@ -88,7 +88,7 @@ export default { } ``` - + ```ts export default { diff --git a/src/content/docs/workers/testing/vitest-integration/get-started/write-your-first-test.mdx b/src/content/docs/workers/testing/vitest-integration/get-started/write-your-first-test.mdx index 0b9a8800320e1c..3ea9875438f55c 100644 --- a/src/content/docs/workers/testing/vitest-integration/get-started/write-your-first-test.mdx +++ b/src/content/docs/workers/testing/vitest-integration/get-started/write-your-first-test.mdx @@ -121,7 +121,7 @@ Save this file, and you are ready to write your first test. If you created a basic Worker via the guide listed above, you should have the following fetch handler in the `src` folder: - + ```js export default { @@ -131,7 +131,7 @@ export default { }; ``` - + ```ts export default { @@ -145,7 +145,7 @@ export default { This Worker receives a request, and returns a response of `"Hello World!"`. In order to test this, create a `test` folder with the following test file: - + ```js import { env, createExecutionContext, waitOnExecutionContext } from "cloudflare:test"; @@ -166,7 +166,7 @@ describe("Hello World worker", () => { }); ``` - + ```ts import { env, createExecutionContext, waitOnExecutionContext } from "cloudflare:test"; @@ -195,7 +195,7 @@ describe("Hello World worker", () => { Add functionality to handle a `404` path on the Worker. This functionality will return the text `Not found` as well as the status code `404`. - + ```js export default { @@ -211,7 +211,7 @@ export default { }; ``` - + ```ts export default { @@ -231,7 +231,7 @@ export default { To test this, add the following to your test file: - + ```js it("responds with not found and proper status for /404", async () => { @@ -246,7 +246,7 @@ it("responds with not found and proper status for /404", async () => { }); ``` - + ```ts it("responds with not found and proper status for /404", async () => { diff --git a/src/content/docs/workers/wrangler/api.mdx b/src/content/docs/workers/wrangler/api.mdx index 51f555eb6037fb..11de81a92ce0e3 100644 --- a/src/content/docs/workers/wrangler/api.mdx +++ b/src/content/docs/workers/wrangler/api.mdx @@ -83,7 +83,7 @@ To wrap up a test suite, call `await worker.stop()` in an `afterAll` function. #### Single Worker example - + ```js const { unstable_dev } = require("wrangler"); @@ -109,7 +109,7 @@ describe("Worker", () => { }); ``` - + ```ts import { unstable_dev } from "wrangler"; @@ -144,7 +144,7 @@ You can test Workers that call other Workers. In the below example, we refer to If you shut down the child Worker prematurely, the parent Worker will not know the child Worker exists and your tests will fail. - + ```js import { unstable_dev } from "wrangler"; @@ -183,7 +183,7 @@ describe("multi-worker testing", () => { }); ``` - + ```ts import { unstable_dev } from "wrangler"; diff --git a/src/content/partials/ai-gateway/create-gateway.mdx b/src/content/partials/ai-gateway/create-gateway.mdx index 8125c91c1e7866..9d75158bf29e75 100644 --- a/src/content/partials/ai-gateway/create-gateway.mdx +++ b/src/content/partials/ai-gateway/create-gateway.mdx @@ -5,7 +5,7 @@ import { TabItem, Tabs } from "~/components" - + To set up an AI Gateway in the dashboard: @@ -15,7 +15,7 @@ To set up an AI Gateway in the dashboard: 4. Enter your **Gateway name**. Note: Gateway name has a 64 character limit. 5. Select **Create**. - + To set up an AI Gateway using the API: diff --git a/src/content/partials/ai-gateway/delete-gateway.mdx b/src/content/partials/ai-gateway/delete-gateway.mdx index 7285156222cf18..e9cc6aa87f81ba 100644 --- a/src/content/partials/ai-gateway/delete-gateway.mdx +++ b/src/content/partials/ai-gateway/delete-gateway.mdx @@ -5,7 +5,7 @@ import { TabItem, Tabs } from "~/components" - + To delete an AI Gateway in the dashboard: @@ -15,7 +15,7 @@ To delete an AI Gateway in the dashboard: 4. Go to **Settings**. 5. For **Delete Gateway**, select **Delete** (and confirm your deletion). - + To delete an AI Gateway, send a [`DELETE` request](/api/operations/aig-config-delete-gateway) to the Cloudflare API. diff --git a/src/content/partials/ai-gateway/edit-gateway.mdx b/src/content/partials/ai-gateway/edit-gateway.mdx index 5862275ca916bf..6a708439c52587 100644 --- a/src/content/partials/ai-gateway/edit-gateway.mdx +++ b/src/content/partials/ai-gateway/edit-gateway.mdx @@ -5,7 +5,7 @@ import { TabItem, Tabs } from "~/components" - + To edit an AI Gateway in the dashboard: @@ -14,7 +14,7 @@ To edit an AI Gateway in the dashboard: 3. Select your gateway. 4. Go to **Settings** and update as needed. - + To edit an AI Gateway, send a [`PUT` request](/api/operations/aig-config-update-gateway) to the Cloudflare API. diff --git a/src/content/partials/cloudflare-for-platforms/get-started-fallback-origin.mdx b/src/content/partials/cloudflare-for-platforms/get-started-fallback-origin.mdx index 594c969728626c..eb20f546407347 100644 --- a/src/content/partials/cloudflare-for-platforms/get-started-fallback-origin.mdx +++ b/src/content/partials/cloudflare-for-platforms/get-started-fallback-origin.mdx @@ -29,7 +29,7 @@ To create your fallback origin: 2. Designate that record as your fallback origin. - + 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com). 2. Select your account and zone. @@ -37,7 +37,7 @@ To create your fallback origin: 4. For **Fallback Origin**, enter the hostname for your fallback origin. 5. Select **Add Fallback Origin**. - + Using the hostname of the record you just created, [update the fallback origin value](/api/operations/custom-hostname-fallback-origin-for-a-zone-update-fallback-origin-for-custom-hostnames). diff --git a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx index 54c898455e7b53..376261a93283e4 100644 --- a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx +++ b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx @@ -30,13 +30,13 @@ After planning for certification and hostname validation, you can create the cus To create a custom hostname: - + - + diff --git a/src/content/partials/cloudflare-one/access/access-group.mdx b/src/content/partials/cloudflare-one/access/access-group.mdx index e5bf7922258539..8859b9f3a4a04d 100644 --- a/src/content/partials/cloudflare-one/access/access-group.mdx +++ b/src/content/partials/cloudflare-one/access/access-group.mdx @@ -7,7 +7,7 @@ import { TabItem, Tabs } from "~/components" To create an Access group: - + 1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Access Groups**. 2. Select **Add a Group**. @@ -22,7 +22,7 @@ To create an Access group: - + Send a `POST` request to the [`/access/groups`](/api/operations/access-groups-create-an-access-group) endpoint: diff --git a/src/content/partials/cloudflare-one/gateway/lists.mdx b/src/content/partials/cloudflare-one/gateway/lists.mdx index 6915e4e6fce743..48500821382a64 100644 --- a/src/content/partials/cloudflare-one/gateway/lists.mdx +++ b/src/content/partials/cloudflare-one/gateway/lists.mdx @@ -25,7 +25,7 @@ You can now use this list in the policy builder by choosing the *in list* operat ## Create a list manually - + 1. In [Zero Trust](https://one.dash.cloudflare.com), go to **My Team** > **Lists**. 2. Select **Create manual list**. @@ -35,7 +35,7 @@ You can now use this list in the policy builder by choosing the *in list* operat - + ```bash curl https://api.cloudflare.com/client/v4/accounts/{account_id}/gateway/lists \ diff --git a/src/content/partials/dns/create-peer-server.mdx b/src/content/partials/dns/create-peer-server.mdx index a3791b3931e1e7..955f4334538af1 100644 --- a/src/content/partials/dns/create-peer-server.mdx +++ b/src/content/partials/dns/create-peer-server.mdx @@ -5,7 +5,7 @@ import { TabItem, Tabs } from "~/components" - + To create a peer server using the dashboard: @@ -20,7 +20,7 @@ To create a peer server using the dashboard: * **Link an existing TSIG**: If desired, link the TSIG you [previously created](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/#1-create-tsig-optional). 6. Select **Create**. - + To create a peer DNS server using the API, send a [POST request](/api/operations/secondary-dns-\(-peer\)-create-peer). diff --git a/src/content/partials/fundamentals/add-account-members.mdx b/src/content/partials/fundamentals/add-account-members.mdx index 13d966edf7b246..23d435c95e8db6 100644 --- a/src/content/partials/fundamentals/add-account-members.mdx +++ b/src/content/partials/fundamentals/add-account-members.mdx @@ -5,7 +5,7 @@ import { TabItem, Tabs } from "~/components" - + To add a member to your account: @@ -30,7 +30,7 @@ To add a member to your account: If a user already has an account with Cloudflare and you have an Enterprise account, you can also select **Direct Add** to add them to your account without sending an email invitation. ::: - + To add a member using the API, send a [`POST` request](/api/operations/account-members-add-member). diff --git a/src/content/partials/fundamentals/edit-member-permissions.mdx b/src/content/partials/fundamentals/edit-member-permissions.mdx index a0022662e782ed..39a47126edc44a 100644 --- a/src/content/partials/fundamentals/edit-member-permissions.mdx +++ b/src/content/partials/fundamentals/edit-member-permissions.mdx @@ -5,7 +5,7 @@ import { TabItem, Tabs } from "~/components" - + To edit member permissions using the dashboard: @@ -16,7 +16,7 @@ To edit member permissions using the dashboard: 5. Select **Continue to summary**. 6. Review the information, then select **Update**. - + To edit member permissions using the API, get a [list of roles](/api/operations/account-roles-list-roles) available for an account. diff --git a/src/content/partials/fundamentals/remove-account-members.mdx b/src/content/partials/fundamentals/remove-account-members.mdx index 0824bd9a2d7704..1ea4bd7c02c4a4 100644 --- a/src/content/partials/fundamentals/remove-account-members.mdx +++ b/src/content/partials/fundamentals/remove-account-members.mdx @@ -5,7 +5,7 @@ import { TabItem, Tabs } from "~/components" - + To revoke a member's access to your account: @@ -15,7 +15,7 @@ To revoke a member's access to your account: 4. Click **Revoke**. 5. Click **Yes, revoke access**. - + To revoke a member's access to your account using the API, send a [`DELETE` request](/api/operations/account-members-remove-member). diff --git a/src/content/partials/fundamentals/view-account-members.mdx b/src/content/partials/fundamentals/view-account-members.mdx index 8656904cfe3004..7ca09ecaeafad2 100644 --- a/src/content/partials/fundamentals/view-account-members.mdx +++ b/src/content/partials/fundamentals/view-account-members.mdx @@ -5,14 +5,14 @@ import { TabItem, Tabs } from "~/components" - + To view members using the dashboard: 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account. 2. Go to **Manage Account** > **Members**. - + To view members using the API, send a [`GET` request](/api/operations/account-members-list-members). diff --git a/src/content/partials/learning-paths/zero-trust/device-profiles.mdx b/src/content/partials/learning-paths/zero-trust/device-profiles.mdx index 43f2b5ad2d1077..b1ef46b97031a4 100644 --- a/src/content/partials/learning-paths/zero-trust/device-profiles.mdx +++ b/src/content/partials/learning-paths/zero-trust/device-profiles.mdx @@ -13,7 +13,7 @@ Set your default device profile to be applicable to a majority of your userbase, To customize the default settings: - + 1. Go to **Settings** > **WARP Client**. @@ -44,7 +44,7 @@ To customize the default settings: - + 1. Update the default device settings profile: diff --git a/src/content/partials/load-balancing/confirm-pool-health.mdx b/src/content/partials/load-balancing/confirm-pool-health.mdx index f17b601d41d9f5..526a5c1af6899c 100644 --- a/src/content/partials/load-balancing/confirm-pool-health.mdx +++ b/src/content/partials/load-balancing/confirm-pool-health.mdx @@ -7,7 +7,7 @@ import { TabItem, Tabs } from "~/components" Before directing any traffic to your pools, make sure that your pools and monitors are set up correctly. The status of your health check will be *unknown* until the results of the first check are available. - + To confirm pool health using the dashboard: @@ -17,7 +17,7 @@ To confirm pool health using the dashboard: For more information on pool and endpoint health statuses, refer to [How a pool becomes unhealthy](/load-balancing/understand-basics/health-details/#how-a-pool-becomes-unhealthy). - + To fetch the latest health status of all pools, use the [List Pools](/api/operations/account-load-balancer-pools-list-pools) command, paying attention to the `healthy` value for pools and origins (endpoints). diff --git a/src/content/partials/magic-transit/static-routes/static-routes3.mdx b/src/content/partials/magic-transit/static-routes/static-routes3.mdx index a1c2ade8019e12..074259cfadc557 100644 --- a/src/content/partials/magic-transit/static-routes/static-routes3.mdx +++ b/src/content/partials/magic-transit/static-routes/static-routes3.mdx @@ -57,7 +57,7 @@ If your use case requires IP prefixes outside RFC 1918, contact your Cloudflare ## ​​Create a static route - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. 2. Go to **{props.one}**. @@ -71,7 +71,7 @@ If your use case requires IP prefixes outside RFC 1918, contact your Cloudflare 10. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**. 11. Select **Add routes** when you are done. - + @@ -109,14 +109,14 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/routes \ ## ​​Edit a static route - + 1. In **Static routes**, select **Edit** next to the route you want to modify. 2. Enter the updated route information. 3. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**. 4. Select **Edit routes** to save the new information when you are done. - + @@ -155,12 +155,12 @@ https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/routes \ ## ​​Delete static route - + 1. In **Static routes**, locate the static route you want to modify and select **Delete**. 2. Confirm the action by selecting the checkbox and select **Delete**. - + diff --git a/src/content/partials/magic-transit/tunnel-endpoints/add-tunnels.mdx b/src/content/partials/magic-transit/tunnel-endpoints/add-tunnels.mdx index 4413728f746f64..eb2d16f17e85fe 100644 --- a/src/content/partials/magic-transit/tunnel-endpoints/add-tunnels.mdx +++ b/src/content/partials/magic-transit/tunnel-endpoints/add-tunnels.mdx @@ -7,7 +7,7 @@ import { Details, Markdown, Render, TabItem, Tabs } from "~/components" - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. 2. Select **{props.two}**. @@ -71,7 +71,7 @@ IPsec tunnels will not function without a pre-shared key (PSK). - + diff --git a/src/content/partials/magic-transit/tunnel-health/update-tunnel-health-checks-frequency.mdx b/src/content/partials/magic-transit/tunnel-health/update-tunnel-health-checks-frequency.mdx index f1a16d780bb8de..674ffbfb5c5c5a 100644 --- a/src/content/partials/magic-transit/tunnel-health/update-tunnel-health-checks-frequency.mdx +++ b/src/content/partials/magic-transit/tunnel-health/update-tunnel-health-checks-frequency.mdx @@ -9,13 +9,13 @@ By default, Cloudflare servers send + 1. Refer to Add tunnels to learn how to create or edit your tunnel. 2. Change the **Health check rate** to your desired rate. For example, *Low*. 3. Save your changes. - + You can adjust the health check frequency by updating your [GRE](/api/operations/magic-gre-tunnels-update-gre-tunnel), [IPsec](/api/operations/magic-ipsec-tunnels-update-ipsec-tunnel), or [CNI](/api/operations/magic-interconnects-update-interconnect) tunnels. diff --git a/src/content/partials/magic-wan/connector/create-site.mdx b/src/content/partials/magic-wan/connector/create-site.mdx index da6855e1e222b1..581c5d39e64134 100644 --- a/src/content/partials/magic-wan/connector/create-site.mdx +++ b/src/content/partials/magic-wan/connector/create-site.mdx @@ -13,7 +13,7 @@ You need to create a site and set up all the settings associated with it before To add a site: - + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. 2. Go to **Magic WAN** > **Sites**. @@ -25,7 +25,7 @@ To add a site: 8. The Connector will be added to your site with an **Interrupt window** defined. The interrupt window is the time period when the Magic WAN Connector software can update, which may result in interruption to existing connections. You can change this later. Refer to [Interrupt window](/magic-wan/configuration/connector/maintenance/interrupt-service-window/) for more details on how to define when the Connector can update its systems. 9. Select **Next** to proceed to creating your WAN and LAN networks. - + @@ -72,7 +72,7 @@ Take note of the site `id` parameter, as you will need it to create WANs and LAN ### 2. Create a WAN - + 1. In **WAN configuration**, select **Create**. You can create one or more [wide area networks (WANs)](https://www.cloudflare.com/learning/network-layer/what-is-a-wan/). Configuring multiple WANs will create multiple IPsec tunnels. This allows the Connector to failover between circuits according to their health. 2. In **Interface name**, enter a descriptive name for your WAN. @@ -89,7 +89,7 @@ Take note of the site `id` parameter, as you will need it to create WANs and LAN 7. Select **Save** when you are finished. - + @@ -118,7 +118,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{sit ### 3. Create a LAN - + 1. In **LAN configuration**, select **Create**. @@ -145,7 +145,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{sit 9. Select **Save and exit** to finish your configuration. Tunnels and static routes will be automatically created and associated with your site once the Magic WAN Connector boots up (refer to the next step). - + diff --git a/src/content/partials/magic-wan/magic-tunnel-health-alerts/magic-tunnel-health-alerts.mdx b/src/content/partials/magic-wan/magic-tunnel-health-alerts/magic-tunnel-health-alerts.mdx index 3b1a8dd6c2c588..615b3496515a7a 100644 --- a/src/content/partials/magic-wan/magic-tunnel-health-alerts/magic-tunnel-health-alerts.mdx +++ b/src/content/partials/magic-wan/magic-tunnel-health-alerts/magic-tunnel-health-alerts.mdx @@ -24,7 +24,7 @@ If a Magic Tunnel health alert is fired, customers can expect the following data ## Set up Magic Tunnel health alerts - + 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. 2. Select **Notifications** > **Add**. @@ -35,7 +35,7 @@ If a Magic Tunnel health alert is fired, customers can expect the following data 7. Select the **Alert Sensitivity Level** threshold. It is predefined for *Medium*, but you can choose between *High*, *Medium*, and *Low*. 8. Select **Create** when you are done. - + An example of the API configuration for Magic Tunnel health alerts is provided below: diff --git a/src/content/partials/ssl/aop-enable-feature.mdx b/src/content/partials/ssl/aop-enable-feature.mdx index 36543ea9db3118..21175723364611 100644 --- a/src/content/partials/ssl/aop-enable-feature.mdx +++ b/src/content/partials/ssl/aop-enable-feature.mdx @@ -9,7 +9,7 @@ Then, enable the Authenticated Origin Pulls feature as an option for your Cloudf This step sets the TLS Client Auth to require Cloudflare to use a client certificate when connecting to your origin server. - + To enable **Authenticated Origin Pulls** in the dashboard: @@ -25,7 +25,7 @@ Note that this step means Authenticated Origin Pulls will be available, but you ::: - + To enable or disable **Authenticated Origin Pulls** with the API, send a [`PATCH`](/api/operations/zone-settings-edit-single-setting) request with `tls_client_auth` as the setting name in the URI path, and the `value` parameter set to your desired setting (`"on"` or `"off"`). diff --git a/src/content/partials/workers/compute-per-request.mdx b/src/content/partials/workers/compute-per-request.mdx index 405abb8ebed711..78671c444b721b 100644 --- a/src/content/partials/workers/compute-per-request.mdx +++ b/src/content/partials/workers/compute-per-request.mdx @@ -7,7 +7,7 @@ import { TabItem, Tabs } from "~/components" Most Workers are a variation on the default Workers flow: - + ```js export default { @@ -17,7 +17,7 @@ export default { }; ``` - + ```ts export default {