--- title: Changelogs image: https://developers.cloudflare.com/cf-twitter-card.png --- [Skip to content](#%5Ftop) # Changelog New updates and improvements at Cloudflare. [ Subscribe to RSS ](https://developers.cloudflare.com/changelog/rss/index.xml) [ View RSS feeds ](https://developers.cloudflare.com/fundamentals/new-features/available-rss-feeds/) All products ![hero image](https://developers.cloudflare.com/_astro/hero.CVYJHPAd_26AMqX.svg) Jan 15, 2025 1. ### [Increased Workflows limits and improved instance queueing.](https://developers.cloudflare.com/changelog/post/2025-01-15-workflows-more-steps/) [ Workflows ](https://developers.cloudflare.com/workflows/) [Workflows](https://developers.cloudflare.com/workflows/) (beta) now allows you to define up to 1024 [steps](https://developers.cloudflare.com/workflows/build/workers-api/#workflowstep). `sleep` steps do not count against this limit. We've also added: * `instanceId` as property to the [WorkflowEvent](https://developers.cloudflare.com/workflows/build/workers-api/#workflowevent) type, allowing you to retrieve the current instance ID from within a running Workflow instance * Improved queueing logic for Workflow instances beyond the current maximum concurrent instances, reducing the cases where instances are stuck in the queued state. * Support for [pause and resume](https://developers.cloudflare.com/workflows/build/workers-api/#pause) for Workflow instances in a queued state. We're continuing to work on increases to the number of concurrent Workflow instances, steps, and support for a new `waitForEvent` API over the coming weeks. Jan 13, 2025 1. ### [WAF Release - 2025-01-13](https://developers.cloudflare.com/changelog/post/2025-01-13-waf-release/) [ WAF ](https://developers.cloudflare.com/waf/) | Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments | | -------------------------- | ----------- | -------------- | --------------------------------------------------------------------------------------------- | --------------- | ---------- | ------------- | | Cloudflare Managed Ruleset | ...f49e5840 | 100704 | Cleo Harmony - Auth Bypass - CVE:CVE-2024-55956, CVE:CVE-2024-55953 | Log | Block | New Detection | | Cloudflare Managed Ruleset | ...a6d43bc2 | 100705 | Sentry - SSRF | Log | Block | New Detection | | Cloudflare Managed Ruleset | ...ce6311bb | 100706 | Apache Struts - Remote Code Execution - CVE:CVE-2024-53677 | Log | Block | New Detection | | Cloudflare Managed Ruleset | ...2233da1f | 100707 | FortiWLM - Remote Code Execution - CVE:CVE-2023-48782, CVE:CVE-2023-34993, CVE:CVE-2023-34990 | Log | Block | New Detection | | Cloudflare Managed Ruleset | ...e31d972a | 100007C\_BETA | Command Injection - Common Attack Commands | Disabled | | | Jan 09, 2025 1. ### [New Rules Overview Interface](https://developers.cloudflare.com/changelog/post/2025-01-09-rules-overview/) [ Rules ](https://developers.cloudflare.com/rules/) **Rules Overview** gives you a single page to manage all your [Cloudflare Rules](https://developers.cloudflare.com/rules/). What you can do: * **See all your rules in one place** – No more clicking around. * **Find rules faster** – Search by name. * **Understand execution order** – See how rules run in sequence. * **Debug easily** – Use [Trace](https://developers.cloudflare.com/rules/trace-request/) without switching tabs. Check it out in [Rules > Overview ↗](https://dash.cloudflare.com/?to=/:account/:zone/rules/overview). Jan 08, 2025 1. ### [Smart Tiered Cache optimizes Load Balancing Pools](https://developers.cloudflare.com/changelog/post/2025-01-08-smart-tiered-cache-for-load-balancing/) [ Cache / CDN ](https://developers.cloudflare.com/cache/) You can now achieve higher cache hit rates and reduce origin load when using [Load Balancing](https://developers.cloudflare.com/load-balancing/) with [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/tiered-cache/). Cloudflare automatically selects a single, optimal tiered data center for all origins in your Load Balancing Pool. #### How it works When you use [Load Balancing](https://developers.cloudflare.com/load-balancing/) with [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/tiered-cache/), Cloudflare analyzes performance metrics across your pool's origins and automatically selects the optimal Upper Tier data center for the entire pool. This means: * **Consistent cache location**: All origins in the pool share the same Upper Tier cache. * **Higher HIT rates**: Requests for the same content hit the cache more frequently. * **Reduced origin requests**: Fewer requests reach your origin servers. * **Improved performance**: Faster response times for cache HITs. #### Example workflow ``` Load Balancing Pool: api-pool ├── Origin 1: api-1.example.com ├── Origin 2: api-2.example.com └── Origin 3: api-3.example.com ↓ Selected Upper Tier: [Optimal data center based on pool performance] ``` #### Get started To get started, enable [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/tiered-cache/) on your zone and configure your [Load Balancing Pool](https://developers.cloudflare.com/load-balancing/). Jan 07, 2025 1. ### [40-60% Faster D1 Worker API Requests](https://developers.cloudflare.com/changelog/post/2025-01-07-d1-faster-query/) [ D1 ](https://developers.cloudflare.com/d1/) Users making [D1](https://developers.cloudflare.com/d1/) requests via the [Workers API](https://developers.cloudflare.com/d1/worker-api/) can see up to a 60% end-to-end latency improvement due to the removal of redundant network round trips needed for each request to a D1 database. ![D1 Worker API latency](https://developers.cloudflare.com/_astro/faster-d1-worker-api.4S7VSUdP_1LmJ72.webp) _p50, p90, and p95 request latency aggregated across entire D1 service. These latencies are a reference point and should not be viewed as your exact workload improvement._ This performance improvement benefits all D1 Worker API traffic, especially cross-region requests where network latency is an outsized latency factor. For example, a user in Europe talking to a database in North America. D1 [location hints](https://developers.cloudflare.com/d1/configuration/data-location/#provide-a-location-hint) can be used to influence the geographic location of a database. For more details on how D1 removed redundant round trips, see the D1 specific release note [entry](https://developers.cloudflare.com/d1/platform/release-notes/#2025-01-07). Jan 06, 2025 1. ### [WAF Release - 2025-01-06](https://developers.cloudflare.com/changelog/post/2025-01-06-waf-release/) [ WAF ](https://developers.cloudflare.com/waf/) | Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments | | ------------------- | ----------- | -------------- | --------------------------------------------------------------------------------------------------------- | --------------- | ---------- | ------------- | | Cloudflare Specials | ...9da08beb | 100678 | Pandora FMS - Remote Code Execution - CVE:CVE-2024-11320 | Log | Block | New Detection | | Cloudflare Specials | ...ecdf3d02 | 100679 | Palo Alto Networks - Remote Code Execution - CVE:CVE-2024-0012, CVE:CVE-2024-9474 | Log | Block | New Detection | | Cloudflare Specials | ...a40f2a35 | 100680 | Ivanti - Command Injection - CVE:CVE-2024-37397 | Log | Block | New Detection | | Cloudflare Specials | ...58ae3c89 | 100681 | Really Simple Security - Auth Bypass - CVE:CVE-2024-10924 | Log | Block | New Detection | | Cloudflare Specials | ...e37f2da6 | 100682 | Magento - XXE - CVE:CVE-2024-34102 | Log | Block | New Detection | | Cloudflare Specials | ...5054c752 | 100683 | CyberPanel - Remote Code Execution - CVE:CVE-2024-51567 | Log | Block | New Detection | | Cloudflare Specials | ...dfe93d7b | 100684 | Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38094, CVE:CVE-2024-38024, CVE:CVE-2024-38023 | Log | Block | New Detection | | Cloudflare Specials | ...1454c856 | 100685 | CyberPanel - Remote Code Execution - CVE:CVE-2024-51568 | Log | Block | New Detection | | Cloudflare Specials | ...e92362e5 | 100686 | Seeyon - Remote Code Execution | Log | Block | New Detection | | Cloudflare Specials | ...b9f1c9f8 | 100687 | WordPress - Remote Code Execution - CVE:CVE-2024-10781, CVE:CVE-2024-10542 | Log | Block | New Detection | | Cloudflare Specials | ...0d7ca374 | 100688 | ProjectSend - Remote Code Execution - CVE:CVE-2024-11680 | Log | Block | New Detection | | Cloudflare Specials | ...a5260b70 | 100689 | Palo Alto GlobalProtect - Remote Code Execution - CVE:CVE-2024-5921 | Log | Block | New Detection | | Cloudflare Specials | ...d007118b | 100690 | Ivanti - Remote Code Execution - CVE:CVE-2024-37404 | Log | Block | New Detection | | Cloudflare Specials | ...c3e49f64 | 100691 | Array Networks - Remote Code Execution - CVE:CVE-2023-28461 | Log | Block | New Detection | | Cloudflare Specials | ...fcc6f5bb | 100692 | CyberPanel - Remote Code Execution - CVE:CVE-2024-51378 | Log | Block | New Detection | | Cloudflare Specials | ...b615335e | 100693 | Symfony Profiler - Auth Bypass - CVE:CVE-2024-50340 | Log | Block | New Detection | | Cloudflare Specials | ...09d08c8a | 100694 | Citrix Virtual Apps - Remote Code Execution - CVE:CVE-2024-8069 | Log | Block | New Detection | | Cloudflare Specials | ...8aafb2f5 | 100695 | MSMQ Service - Remote Code Execution - CVE:CVE-2023-21554 | Log | Block | New Detection | | Cloudflare Specials | ...11b7a8c7 | 100696 | Nginxui - Remote Code Execution - CVE:CVE-2024-49368 | Log | Block | New Detection | | Cloudflare Specials | ...45954c7e | 100697 | Apache ShardingSphere - Remote Code Execution - CVE:CVE-2022-22733 | Log | Block | New Detection | | Cloudflare Specials | ...f5311209 | 100698 | Mitel MiCollab - Auth Bypass - CVE:CVE-2024-41713 | Log | Block | New Detection | | Cloudflare Specials | ...b3e5e46e | 100699 | Apache Solr - Auth Bypass - CVE:CVE-2024-45216 | Log | Block | New Detection | Jan 02, 2025 1. ### [AI Gateway adds DeepSeek as a Provider](https://developers.cloudflare.com/changelog/post/2025-01-07-aig-provider-deepseek/) [ AI Gateway ](https://developers.cloudflare.com/ai-gateway/) [**AI Gateway**](https://developers.cloudflare.com/ai-gateway/) now supports [**DeepSeek**](https://developers.cloudflare.com/ai-gateway/usage/providers/deepseek/), including their cutting-edge DeepSeek-V3 model. With this addition, you have even more flexibility to manage and optimize your AI workloads using AI Gateway. Whether you're leveraging DeepSeek or other providers, like OpenAI, Anthropic, or [Workers AI](https://developers.cloudflare.com/workers-ai/), AI Gateway empowers you to: * **Monitor**: Gain actionable insights with analytics and logs. * **Control**: Implement caching, rate limiting, and fallbacks. * **Optimize**: Improve performance with feedback and evaluations. ![AI Gateway adds DeepSeek as a provider](https://developers.cloudflare.com/_astro/deepseek.hirkr3rv_CgMEY.webp) To get started, simply update the base URL of your DeepSeek API calls to route through AI Gateway. Here's how you can send a request using cURL: Example fetch request ``` curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepseek/chat/completions \ --header 'content-type: application/json' \ --header 'Authorization: Bearer DEEPSEEK_TOKEN' \ --data '{ "model": "deepseek-chat", "messages": [ { "role": "user", "content": "What is Cloudflare?" } ] }' ``` Explain Code For detailed setup instructions, see our [DeepSeek provider documentation](https://developers.cloudflare.com/ai-gateway/usage/providers/deepseek/). Dec 29, 2024 1. ### [Faster Workers Builds with Build Caching and Watch Paths](https://developers.cloudflare.com/changelog/post/2024-12-29-faster-builds/) [ Workers ](https://developers.cloudflare.com/workers/) ![Build caching settings](https://developers.cloudflare.com/_astro/workers-build-caching.DWEh3Tj1_Z1HXvDQ.webp)![Build watch path settings](https://developers.cloudflare.com/_astro/workers-build-watch-paths.ClqD-iNq_ZUCGHo.webp) [**Workers Builds**](https://developers.cloudflare.com/workers/ci-cd/builds/), the integrated CI/CD system for Workers (currently in beta), now lets you cache artifacts across builds, speeding up build jobs by eliminating repeated work, such as downloading dependencies at the start of each build. * **[Build Caching](https://developers.cloudflare.com/workers/ci-cd/builds/build-caching/)**: Cache dependencies and build outputs between builds with a shared project-wide cache, ensuring faster builds for the entire team. * **[Build Watch Paths](https://developers.cloudflare.com/workers/ci-cd/builds/build-watch-paths/)**: Define paths to include or exclude from the build process, ideal for [monorepos](https://developers.cloudflare.com/workers/ci-cd/builds/advanced-setups/#monorepos) to target only the files that need to be rebuilt per Workers project. To get started, select your Worker on the [Cloudflare dashboard ↗](https://dash.cloudflare.com) then go to **Settings** \> **Builds**, and connect a GitHub or GitLab repository. Once connected, you'll see options to configure Build Caching and Build Watch Paths. Dec 19, 2024 1. ### [Escalate user submissions](https://developers.cloudflare.com/changelog/post/2024-12-19-escalate-user-submissions/) [ Email security ](https://developers.cloudflare.com/cloudflare-one/email-security/) After you triage your users' submissions (that are machine reviewed), you can now escalate them to our team for reclassification (which are instead human reviewed). User submissions from the submission alias, PhishNet, and our API can all be escalated. ![Escalate](https://developers.cloudflare.com/_astro/Escalate.CwXPIyM3_ZxuRN6.webp) From **Reclassifications**, go to **User submissions**. Select the three dots next to any of the user submissions, then select **Escalate** to create a team request for reclassification. The Cloudflare dashboard will then show you the submissions on the **Team Submissions** tab. Refer to [User submissions](https://developers.cloudflare.com/cloudflare-one/email-security/submissions/user-submissions/) to learn more about this feature. This feature is available across these Email security packages: * **Advantage** * **Enterprise** * **Enterprise + PhishGuard** Dec 19, 2024 1. ### [Increased transparency for phishing email submissions](https://developers.cloudflare.com/changelog/post/2024-12-19-reclassification-tab/) [ Email security ](https://developers.cloudflare.com/cloudflare-one/email-security/) You now have more transparency about team and user submissions for phishing emails through a **Reclassification** tab in the Zero Trust dashboard. Reclassifications happen when users or admins [submit a phish](https://developers.cloudflare.com/cloudflare-one/email-security/settings/phish-submissions/) to Email security. Cloudflare reviews and - in some cases - reclassifies these emails based on improvements to our machine learning models. This new tab increases your visibility into this process, allowing you to view what submissions you have made and what the outcomes of those submissions are. ![Use the Reclassification area to review submitted phishing emails](https://developers.cloudflare.com/_astro/reclassifications-tab.yDgtjG51_Z1TVbIE.webp) Dec 19, 2024 1. ### [Troubleshoot tunnels with diagnostic logs](https://developers.cloudflare.com/changelog/post/2024-12-19-diagnostic-logs/) [ Cloudflare Tunnel ](https://developers.cloudflare.com/tunnel/)[ Cloudflare Tunnel for SASE ](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/) The latest `cloudflared` build [2024.12.2 ↗](https://github.com/cloudflare/cloudflared/releases/tag/2024.12.2) introduces the ability to collect all the diagnostic logs needed to troubleshoot a `cloudflared` instance. A diagnostic report collects data from a single instance of `cloudflared` running on the local machine and outputs it to a `cloudflared-diag` file. For more information, refer to [Diagnostic logs](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/diag-logs/). Dec 17, 2024 1. ### [Establish BGP peering over Direct CNI circuits](https://developers.cloudflare.com/changelog/post/2024-12-17-bgp-support-cni/) [ Magic Transit ](https://developers.cloudflare.com/magic-transit/)[ Cloudflare WAN ](https://developers.cloudflare.com/cloudflare-wan/)[ Network Interconnect ](https://developers.cloudflare.com/network-interconnect/) Magic WAN and Magic Transit customers can use the Cloudflare dashboard to configure and manage BGP peering between their networks and their Magic routing table when using a Direct CNI on-ramp. Using BGP peering allows customers to: * Automate the process of adding or removing networks and subnets. * Take advantage of failure detection and session recovery features. With this functionality, customers can: * Establish an eBGP session between their devices and the Magic WAN / Magic Transit service when connected via CNI. * Secure the session by MD5 authentication to prevent misconfigurations. * Exchange routes dynamically between their devices and their Magic routing table. Refer to [Magic WAN BGP peering](https://developers.cloudflare.com/cloudflare-wan/configuration/manually/how-to/configure-routes/#configure-bgp-routes) or [Magic Transit BGP peering](https://developers.cloudflare.com/magic-transit/how-to/configure-routes/#configure-bgp-routes) to learn more about this feature and how to set it up. Dec 11, 2024 1. ### [Up to 10x faster cached queries for Hyperdrive](https://developers.cloudflare.com/changelog/post/2024-12-11-hyperdrive-caching-at-edge/) [ Hyperdrive ](https://developers.cloudflare.com/hyperdrive/) Hyperdrive now caches queries in all Cloudflare locations, decreasing cache hit latency by up to 90%. When you make a query to your database and Hyperdrive has cached the query results, Hyperdrive will now return the results from the nearest cache. By caching data closer to your users, the latency for cache hits reduces by up to 90%. This reduction in cache hit latency is reflected in a reduction of the session duration for all queries (cached and uncached) from Cloudflare Workers to Hyperdrive, as illustrated below. ![Hyperdrive edge caching improves average session duration for database queries](https://developers.cloudflare.com/_astro/hyperdrive-edge-caching-metrics.BR7svphB_2kl758.webp) _P50, P75, and P90 Hyperdrive session latency for all client connection sessions (both cached and uncached queries) for Hyperdrive configurations with caching enabled during the rollout period._ This performance improvement is applied to all new and existing Hyperdrive configurations that have caching enabled. For more details on how Hyperdrive performs query caching, refer to the [Hyperdrive documentation](https://developers.cloudflare.com/hyperdrive/concepts/how-hyperdrive-works/#3-query-caching). Dec 11, 2024 1. ### [Terraform Support for Snippets](https://developers.cloudflare.com/changelog/post/2024-12-11-terraform-snippets/) [ Rules ](https://developers.cloudflare.com/rules/) Now, you can manage [Cloudflare Snippets](https://developers.cloudflare.com/rules/snippets/) with [Terraform](https://developers.cloudflare.com/terraform/). Use infrastructure-as-code to deploy and update Snippet code and rules without manual changes in the dashboard. Example Terraform configuration: ``` resource "cloudflare_snippet" "my_snippet" { zone_id = "" name = "my_test_snippet_1" main_module = "file1.js" files { name = "file1.js" content = file("file1.js") } } resource "cloudflare_snippet_rules" "cookie_snippet_rule" { zone_id = "" rules { enabled = true expression = "http.cookie eq \"a=b\"" description = "Trigger snippet on specific cookie" snippet_name = "my_test_snippet_1" } depends_on = [cloudflare_snippet.my_snippet] } ``` Explain Code Learn more in the [Configure Snippets using Terraform](https://developers.cloudflare.com/rules/snippets/create-terraform/) documentation. Dec 05, 2024 1. ### [Generate customized terraform files for building cloud network on-ramps](https://developers.cloudflare.com/changelog/post/2024-12-05-cloud-onramp-terraform/) [ Multi-Cloud Networking ](https://developers.cloudflare.com/multi-cloud-networking/) You can now generate customized terraform files for building cloud network on-ramps to [Magic WAN](https://developers.cloudflare.com/cloudflare-wan/). [Magic Cloud](https://developers.cloudflare.com/multi-cloud-networking/) can scan and discover existing network resources and generate the required terraform files to automate cloud resource deployment using their existing infrastructure-as-code workflows for cloud automation. You might want to do this to: * Review the proposed configuration for an on-ramp before deploying it with Cloudflare. * Deploy the on-ramp using your own infrastructure-as-code pipeline instead of deploying it with Cloudflare. For more details, refer to [Set up with Terraform](https://developers.cloudflare.com/multi-cloud-networking/cloud-on-ramps/#set-up-with-terraform). Nov 22, 2024 1. ### [Find security misconfigurations in your AWS cloud environment](https://developers.cloudflare.com/changelog/post/2024-11-22-cloud-data-extraction-aws/) [ CASB ](https://developers.cloudflare.com/cloudflare-one/integrations/cloud-and-saas/) You can now use CASB to find security misconfigurations in your AWS cloud environment using [Data Loss Prevention](https://developers.cloudflare.com/cloudflare-one/data-loss-prevention/). You can also [connect your AWS compute account](https://developers.cloudflare.com/cloudflare-one/integrations/cloud-and-saas/aws-s3/#compute-account) to extract and scan your S3 buckets for sensitive data while avoiding egress fees. CASB will scan any objects that exist in the bucket at the time of configuration. To connect a compute account to your AWS integration: 1. In [Cloudflare One ↗](https://one.dash.cloudflare.com), go to **Cloud & SaaS findings** \> **Integrations**. 2. Find and select your AWS integration. 3. Select **Open connection instructions**. 4. Follow the instructions provided to connect a new compute account. 5. Select **Refresh**. Nov 22, 2024 1. ### [Cloud Connector Now Supports R2](https://developers.cloudflare.com/changelog/post/2024-11-22-cloud-connector-r2/) [ Rules ](https://developers.cloudflare.com/rules/) Now, you can use [Cloud Connector](https://developers.cloudflare.com/rules/cloud-connector/) to route traffic to your [R2 buckets](https://developers.cloudflare.com/r2/) based on URLs, headers, geolocation, and more. Example setup: Terminal window ``` curl --request PUT \ "https://api.cloudflare.com/client/v4/zones/{zone_id}/cloud_connector/rules" \ --header "Authorization: Bearer " \ --header "Content-Type: application/json" \ --data '[ { "expression": "http.request.uri.path wildcard \"/images/*\"", "provider": "cloudflare_r2", "description": "Connect to R2 bucket containing images", "parameters": { "host": "mybucketcustomdomain.example.com" } } ]' ``` Explain Code Get started using [Cloud Connector](https://developers.cloudflare.com/rules/cloud-connector/) documentation. Nov 21, 2024 1. ### [Improved non-English keyboard support](https://developers.cloudflare.com/changelog/post/2024-11-21-non-english-keyboard/) [ Browser Isolation ](https://developers.cloudflare.com/cloudflare-one/remote-browser-isolation/) You can now type in languages that use diacritics (like á or ç) and character-based scripts (such as Chinese, Japanese, and Korean) directly within the remote browser. The isolated browser now properly recognizes non-English keyboard input, eliminating the need to copy and paste content from a local browser or device. Nov 20, 2024 1. ### [Smart Tiered Cache automatically optimizes R2 caching](https://developers.cloudflare.com/changelog/post/2024-11-20-smart-tiered-cache-for-r2/) [ Cache / CDN ](https://developers.cloudflare.com/cache/) You can now reduce latency and lower R2 egress costs automatically when using [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/tiered-cache/) with [R2](https://developers.cloudflare.com/r2/). Cloudflare intelligently selects a tiered data center close to your R2 bucket location, creating an efficient caching topology without additional configuration. #### How it works When you enable [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/tiered-cache/) for zones using [R2](https://developers.cloudflare.com/r2/) as an origin, Cloudflare automatically: 1. **Identifies your R2 bucket location**: Determines the geographical region where your R2 bucket is stored. 2. **Selects an optimal Upper Tier**: Chooses a data center close to your bucket as the common Upper Tier cache. 3. **Routes requests efficiently**: All cache misses in edge locations route through this Upper Tier before reaching R2. #### Benefits * **Automatic optimization**: No manual configuration required. * **Lower egress costs**: Fewer requests to R2 reduce egress charges. * **Improved hit ratio**: Common Upper Tier increases cache efficiency. * **Reduced latency**: Upper Tier proximity to R2 minimizes fetch times. #### Get started To get started, enable [Smart Tiered Cache](https://developers.cloudflare.com/cache/how-to/tiered-cache/) on your zone using R2 as an origin. Nov 11, 2024 1. ### [Bypass caching for subrequests made from Cloudflare Workers, with Request.cache](https://developers.cloudflare.com/changelog/post/2024-11-11-cache-no-store/) [ Workers ](https://developers.cloudflare.com/workers/) You can now use the [cache](https://developers.cloudflare.com/workers/runtime-apis/request/#options) property of the [Request](https://developers.cloudflare.com/workers/runtime-apis/request/) interface to bypass [Cloudflare's cache](https://developers.cloudflare.com/workers/reference/how-the-cache-works/) when making subrequests from [Cloudflare Workers](https://developers.cloudflare.com/workers), by setting its value to `no-store`. * [ JavaScript ](#tab-panel-2860) * [ TypeScript ](#tab-panel-2861) index.js ``` export default { async fetch(req, env, ctx) { const request = new Request("https://cloudflare.com", { cache: "no-store", }); const response = await fetch(request); return response; }, }; ``` index.ts ``` export default { async fetch(req, env, ctx): Promise { const request = new Request("https://cloudflare.com", { cache: 'no-store'}); const response = await fetch(request); return response; } } satisfies ExportedHandler ``` When you set the value to `no-store` on a subrequest made from a Worker, the Cloudflare Workers runtime will not check whether a match exists in the cache, and not add the response to the cache, even if the response includes directives in the `Cache-Control` HTTP header that otherwise indicate that the response is cacheable. This increases compatibility with NPM packages and JavaScript frameworks that rely on setting the [cache](https://developers.cloudflare.com/workers/runtime-apis/request/#options) property, which is a cross-platform standard part of the [Request](https://developers.cloudflare.com/workers/runtime-apis/request/) interface. Previously, if you set the `cache` property on `Request`, the Workers runtime threw an exception. If you've tried to use `@planetscale/database`, `redis-js`, `stytch-node`, `supabase`, `axiom-js` or have seen the error message `The cache field on RequestInitializerDict is not implemented in fetch` — you should try again, making sure that the [Compatibility Date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) of your Worker is set to on or after `2024-11-11`, or the [cache\_option\_enabled compatibility flag](https://developers.cloudflare.com/workers/configuration/compatibility-flags/#enable-cache-no-store-http-standard-api) is enabled for your Worker. * Learn [how the Cache works with Cloudflare Workers](https://developers.cloudflare.com/workers/reference/how-the-cache-works/) * Enable [Node.js compatibility](https://developers.cloudflare.com/workers/runtime-apis/nodejs/) for your Cloudflare Worker * Explore [Runtime APIs](https://developers.cloudflare.com/workers/runtime-apis/) and [Bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/) available in Cloudflare Workers Nov 07, 2024 1. ### [Use Logpush for Email security user actions](https://developers.cloudflare.com/changelog/post/2024-11-07-logpush-user-actions/) [ Email security ](https://developers.cloudflare.com/cloudflare-one/email-security/) You can now send user action logs for Email security to an endpoint of your choice with Cloudflare Logpush. Filter logs matching specific criteria you have set or select from multiple fields you want to send. For all users, we will log the date and time, user ID, IP address, details about the message they accessed, and what actions they took. When creating a new Logpush job, remember to select **Audit logs** as the dataset and filter by: * **Field**: `"ResourceType"` * **Operator**: `"starts with"` * **Value**: `"email_security"`. ![Logpush-user-actions](https://developers.cloudflare.com/_astro/Logpush-User-Actions.D14fWgmq_CYM35.webp) For more information, refer to [Enable user action logs](https://developers.cloudflare.com/cloudflare-one/insights/logs/logpush/email-security-logs/#enable-user-action-logs). This feature is available across all Email security packages: * **Enterprise** * **Enterprise + PhishGuard** Nov 07, 2024 1. ### [Stage and test cache configurations safely](https://developers.cloudflare.com/changelog/post/2024-11-07-cache-versioning/) [ Cache / CDN ](https://developers.cloudflare.com/cache/) You can now stage and test cache configurations before deploying them to production. Versioned environments let you safely validate cache rules, purge operations, and configuration changes without affecting live traffic. #### How it works With versioned environments, you can: 1. **Create staging versions** of your cache configuration. 2. **Test cache rules** in a non-production environment. 3. **Purge staged content** independently from production. 4. **Validate changes** before promoting to production. This capability integrates with Cloudflare's broader [versioning system](https://developers.cloudflare.com/version-management/), allowing you to manage cache configurations alongside other zone settings. #### Benefits * **Risk-free testing**: Validate configuration changes without impacting production. * **Independent purging**: Clear staging cache without affecting live content. * **Deployment confidence**: Catch issues before they reach end users. * **Team collaboration**: Multiple team members can work on different versions. #### Get started To get started, refer to the [version management documentation](https://developers.cloudflare.com/version-management/). Important limitation Cache Reserve is only supported for your production environment. Staged environments can use standard cache functionality, but Cache Reserve persistence is limited to production deployments. Nov 07, 2024 1. ### [Shard cache using custom cache key values](https://developers.cloudflare.com/changelog/post/2024-11-07-shard-cache-by-cache-key/) [ Cache / CDN ](https://developers.cloudflare.com/cache/) Enterprise customers can now optimize cache hit ratios for content that varies by device, language, or referrer by **sharding cache** using up to ten values from previously restricted headers with [custom cache keys](https://developers.cloudflare.com/cache/how-to/cache-keys/). #### How it works When configuring [custom cache keys](https://developers.cloudflare.com/cache/how-to/cache-keys/), you can now include values from these headers to create distinct cache entries: * **`accept*` headers** (for example, `accept`, `accept-encoding`, `accept-language`): Serve different cached versions based on content negotiation. * **`referer` header**: Cache content differently based on the referring page or site. * **`user-agent` header**: Maintain separate caches for different browsers, devices, or bots. #### When to use cache sharding * Content varies significantly by device type (mobile vs desktop). * Different language or encoding preferences require distinct responses. * Referrer-specific content optimization is needed. #### Example configuration ``` { "cache_key": { "custom_key": { "header": { "include": ["accept-language", "user-agent"], "check_presence": ["referer"] } } } } ``` Explain Code This configuration creates separate cache entries based on the `accept-language` and `user-agent` headers, while also considering whether the `referer` header is present. #### Get started To get started, refer to the [custom cache keys documentation](https://developers.cloudflare.com/cache/how-to/cache-keys/). Note While cache sharding can improve hit ratios for specific use cases, overly sharding your cache can reduce overall cache efficiency and negatively impact performance. Carefully evaluate whether sharding benefits your specific traffic patterns. Oct 24, 2024 1. ### [Workflows is now in open beta](https://developers.cloudflare.com/changelog/post/2024-10-24-workflows-beta/) [ Workers ](https://developers.cloudflare.com/workers/)[ Workflows ](https://developers.cloudflare.com/workflows/) Workflows is now in open beta, and available to any developer a free or paid Workers plan. Workflows allow you to build multi-step applications that can automatically retry, persist state and run for minutes, hours, days, or weeks. Workflows introduces a programming model that makes it easier to build reliable, long-running tasks, observe as they progress, and programmatically trigger instances based on events across your services. #### Get started You can get started with Workflows by [following our get started guide](https://developers.cloudflare.com/workflows/get-started/guide/) and/or using `npm create cloudflare` to pull down the starter project: Terminal window ``` npm create cloudflare@latest workflows-starter -- --template "cloudflare/workflows-starter" ``` You can open the `src/index.ts` file, extend it, and use `wrangler deploy` to deploy your first Workflow. From there, you can: * Learn the [Workflows API](https://developers.cloudflare.com/workflows/build/workers-api/) * [Trigger Workflows](https://developers.cloudflare.com/workflows/build/trigger-workflows/) via your Workers apps. * Understand the [Rules of Workflows](https://developers.cloudflare.com/workflows/build/rules-of-workflows/) and how to adopt best practices Oct 23, 2024 1. ### [Simplified UI for URL Rewrites](https://developers.cloudflare.com/changelog/post/2024-10-23-url-rewrites-wildcard/) [ Rules ](https://developers.cloudflare.com/rules/) It’s now easy to create **wildcard-based [URL Rewrites](https://developers.cloudflare.com/rules/transform/url-rewrite/)**. No need for complex functions—just define your patterns and go. ![Rules Overview Interface](https://developers.cloudflare.com/_astro/create-url-rewrite-rule.DIgpB8IB_ZNTjfK.webp) What’s improved: * **Full wildcard support** – Create rewrite patterns using intuitive interface. * **Simplified rule creation** – No need for complex functions. Try it via [creating a Rewrite URL rule in the dashboard](https://developers.cloudflare.com/rules/transform/url-rewrite/create-dashboard/#wildcard-pattern-parameters). [Search all changelog entries](https://developers.cloudflare.com/search/?contentType=Changelog+entry)