--- title: Changelogs image: https://edgetunnel-b2h.pages.dev/cf-twitter-card.png --- > Documentation Index > Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt > Use this file to discover all available pages before exploring further. [Skip to content](#%5Ftop) # Changelog New updates and improvements at Cloudflare. [ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) All products ![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) Feb 26, 2025 1. ### [Introducing Guardrails in AI Gateway](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-26-guardrails/) [ AI Gateway ](https://edgetunnel-b2h.pages.dev/ai-gateway/) [AI Gateway](https://edgetunnel-b2h.pages.dev/ai-gateway/) now includes [Guardrails](https://edgetunnel-b2h.pages.dev/ai-gateway/features/guardrails/), to help you monitor your AI apps for harmful or inappropriate content and deploy safely. Within the AI Gateway settings, you can configure: * **Guardrails**: Enable or disable content moderation as needed. * **Evaluation scope**: Select whether to moderate user prompts, model responses, or both. * **Hazard categories**: Specify which categories to monitor and determine whether detected inappropriate content should be blocked or flagged. ![Guardrails in AI Gateway](https://edgetunnel-b2h.pages.dev/_astro/Guardrails.BTNc0qeC_Z1HC20z.webp) Learn more in the [blog ↗](https://blog.cloudflare.com/guardrails-in-ai-gateway/) or our [documentation](https://edgetunnel-b2h.pages.dev/ai-gateway/features/guardrails/). Feb 25, 2025 1. ### [Use DLP Assist for M365](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-25-dlp-assist-for-m365/) [ Email security ](https://edgetunnel-b2h.pages.dev/cloudflare-one/email-security/) Cloudflare Email security customers who have Microsoft 365 environments can quickly deploy an Email DLP (Data Loss Prevention) solution for free. Simply deploy our add-in, create a DLP policy in Cloudflare, and configure Outlook to trigger behaviors like displaying a banner, alerting end users before sending, or preventing delivery entirely. Refer to [Outbound Data Loss Prevention](https://edgetunnel-b2h.pages.dev/cloudflare-one/email-security/outbound-dlp/) to learn more about this feature. In GUI alert: ![DLP-Alert](https://edgetunnel-b2h.pages.dev/_astro/DLP-Alert.5s-fbKn3_1xfB14.webp) Alert before sending: ![DLP-Pop-up](https://edgetunnel-b2h.pages.dev/_astro/DLP-Pop-up.0gkYy7o5_ZgIo8K.webp) Prevent delivery: ![DLP-Blocked](https://edgetunnel-b2h.pages.dev/_astro/DLP-Blocked.CmQkGrnM_ZewJi3.webp) This feature is available across these Email security packages: * **Enterprise** * **Enterprise + PhishGuard** Feb 25, 2025 1. ### [Introducing the Agents SDK](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-25-agents-sdk/) [ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/) We've released the [Agents SDK ↗](http://blog.cloudflare.com/build-ai-agents-on-cloudflare/), a package and set of tools that help you build and ship AI Agents. You can get up and running with a [chat-based AI Agent ↗](https://github.com/cloudflare/agents-starter) (and deploy it to Workers) that uses the Agents SDK, tool calling, and state syncing with a React-based front-end by running the following command: ```sh npm create cloudflare@latest agents-starter -- --template="cloudflare/agents-starter" # open up README.md and follow the instructions ``` You can also add an Agent to any existing Workers application by installing the `agents` package directly ```sh npm i agents ``` ... and then define your first Agent: **TypeScript** ```ts import { Agent } from "agents"; export class YourAgent extends Agent { // Build it out // Access state on this.state or query the Agent's database via this.sql // Handle WebSocket events with onConnect and onMessage // Run tasks on a schedule with this.schedule // Call AI models // ... and/or call other Agents. } ``` Head over to the [Agents documentation](https://edgetunnel-b2h.pages.dev/agents/) to learn more about the Agents SDK, the SDK APIs, as well as how to test and deploying agents to production. Feb 25, 2025 1. ### [Workers AI now supports structured JSON outputs.](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-25-json-mode/) [ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/) Workers AI now supports structured JSON outputs with [JSON mode](https://edgetunnel-b2h.pages.dev/workers-ai/features/json-mode/), which allows you to request a structured output response when interacting with AI models. This makes it much easier to retrieve structured data from your AI models, and avoids the (error prone!) need to parse large unstructured text responses to extract your data. JSON mode in Workers AI is compatible with the OpenAI SDK's [structured outputs ↗](https://platform.openai.com/docs/guides/structured-outputs) `response_format` API, which can be used directly in a Worker: * [ JavaScript ](#tab-panel-5183) * [ TypeScript ](#tab-panel-5184) **JavaScript** ```js import { OpenAI } from "openai"; // Define your JSON schema for a calendar event const CalendarEventSchema = { type: "object", properties: { name: { type: "string" }, date: { type: "string" }, participants: { type: "array", items: { type: "string" } }, }, required: ["name", "date", "participants"], }; export default { async fetch(request, env) { const client = new OpenAI({ apiKey: env.OPENAI_API_KEY, // Optional: use AI Gateway to bring logs, evals & caching to your AI requests // https://edgetunnel-b2h.pages.dev/ai-gateway/usage/providers/openai/ // baseUrl: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai" }); const response = await client.chat.completions.create({ model: "gpt-4o-2024-08-06", messages: [ { role: "system", content: "Extract the event information." }, { role: "user", content: "Alice and Bob are going to a science fair on Friday.", }, ], // Use the `response_format` option to request a structured JSON output response_format: { // Set json_schema and provide ra schema, or json_object and parse it yourself type: "json_schema", schema: CalendarEventSchema, // provide a schema }, }); // This will be of type CalendarEventSchema const event = response.choices[0].message.parsed; return Response.json({ calendar_event: event, }); }, }; ``` **TypeScript** ```ts import { OpenAI } from "openai"; interface Env { OPENAI_API_KEY: string; } // Define your JSON schema for a calendar event const CalendarEventSchema = { type: "object", properties: { name: { type: "string" }, date: { type: "string" }, participants: { type: "array", items: { type: "string" } }, }, required: ["name", "date", "participants"], }; export default { async fetch(request: Request, env: Env) { const client = new OpenAI({ apiKey: env.OPENAI_API_KEY, // Optional: use AI Gateway to bring logs, evals & caching to your AI requests // https://edgetunnel-b2h.pages.dev/ai-gateway/usage/providers/openai/ // baseUrl: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai" }); const response = await client.chat.completions.create({ model: "gpt-4o-2024-08-06", messages: [ { role: "system", content: "Extract the event information." }, { role: "user", content: "Alice and Bob are going to a science fair on Friday.", }, ], // Use the `response_format` option to request a structured JSON output response_format: { // Set json_schema and provide ra schema, or json_object and parse it yourself type: "json_schema", schema: CalendarEventSchema, // provide a schema }, }); // This will be of type CalendarEventSchema const event = response.choices[0].message.parsed; return Response.json({ calendar_event: event, }); }, }; ``` To learn more about JSON mode and structured outputs, visit the [Workers AI documentation](https://edgetunnel-b2h.pages.dev/workers-ai/features/json-mode/). Feb 25, 2025 1. ### [Concurrent Workflow instances limits increased.](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-25-workflows-concurrency-increased/) [ Workflows ](https://edgetunnel-b2h.pages.dev/workflows/) [Workflows](https://edgetunnel-b2h.pages.dev/workflows/) now supports up to 4,500 concurrent (running) instances, up from the previous limit of 100\. This limit will continue to increase during the Workflows open beta. This increase applies to all users on the Workers Paid plan, and takes effect immediately. Review the Workflows [limits documentation](https://edgetunnel-b2h.pages.dev/workflows/reference/limits) and/or dive into the [get started guide](https://edgetunnel-b2h.pages.dev/workflows/get-started/guide/) to start building on Workflows. Feb 24, 2025 1. ### [Bind the Images API to your Worker](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-21-images-bindings-in-workers/) [ Cloudflare Images ](https://edgetunnel-b2h.pages.dev/images/) You can now [interact with the Images API](https://edgetunnel-b2h.pages.dev/images/optimization/binding/) directly in your Worker. This allows more fine-grained control over transformation request flows and cache behavior. For example, you can resize, manipulate, and overlay images without requiring them to be accessible through a URL. The Images binding can be configured in the Cloudflare dashboard for your Worker or in the Wrangler configuration file in your project's directory: * [ wrangler.jsonc ](#tab-panel-5181) * [ wrangler.toml ](#tab-panel-5182) **JSONC** ```jsonc { "images": { "binding": "IMAGES", // i.e. available in your Worker on env.IMAGES }, } ``` **TOML** ```toml [images] binding = "IMAGES" ``` Within your Worker code, you can interact with this binding by using `env.IMAGES`. Here's how you can rotate, resize, and blur an image, then output the image as AVIF: **TypeScript** ```ts const info = await env.IMAGES.info(stream); // stream contains a valid image, and width/height is available on the info object const response = ( await env.IMAGES.input(stream) .transform({ rotate: 90 }) .transform({ width: 128 }) .transform({ blur: 20 }) .output({ format: "image/avif" }) ).response(); return response; ``` For more information, refer to [Images Bindings](https://edgetunnel-b2h.pages.dev/images/optimization/binding/). Feb 24, 2025 1. ### [Super Slurper now supports migrations from all S3-compatible storage providers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-24-r2-super-slurper-s3-compatible-support/) [ R2 ](https://edgetunnel-b2h.pages.dev/r2/) [Super Slurper](https://edgetunnel-b2h.pages.dev/r2/data-migration/super-slurper/) can now migrate data from any S3-compatible object storage provider to [Cloudflare R2](https://edgetunnel-b2h.pages.dev/r2/). This includes transfers from services like MinIO, Wasabi, Backblaze B2, and DigitalOcean Spaces. ![Super Slurper S3-Compatible Source](https://edgetunnel-b2h.pages.dev/_astro/super-slurper-s3-compat-screenshot-border.D8Gd5eye_dt8CT.webp) For more information on Super Slurper and how to migrate data from your existing S3-compatible storage buckets to R2, refer to our [documentation](https://edgetunnel-b2h.pages.dev/r2/data-migration/super-slurper/). Feb 24, 2025 1. ### [WAF Release - 2025-02-24](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-24-waf-release/) [ WAF ](https://edgetunnel-b2h.pages.dev/waf/) | Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments | | -------------------------- | ----------- | -------------- | ----------------------------------------------------- | --------------- | ---------- | ----------------------- | | Cloudflare Managed Ruleset | ...4916911e | 100718A | SonicWall SSLVPN 2 - Auth Bypass - CVE:CVE-2024-53704 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...c382fdec | 100720 | Palo Alto Networks - Auth Bypass - CVE:CVE-2025-0108 | Log | Block | This is a New Detection | Feb 24, 2025 1. ### [Workers AI larger context windows](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-24-context-windows/) [ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/) We've updated the Workers AI text generation models to include context windows and limits definitions and changed our APIs to estimate and validate the number of tokens in the input prompt, not the number of characters. This update allows developers to use larger context windows when interacting with Workers AI models, which can lead to better and more accurate results. Our [catalog page](https://edgetunnel-b2h.pages.dev/workers-ai/models/) provides more information about each model's supported context window. Feb 24, 2025 1. ### [Zaraz moves to the “Tag Management” category in the Cloudflare dashboard](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-24-zaraz-dash-placement/) [ Zaraz ](https://edgetunnel-b2h.pages.dev/zaraz/) ![Zaraz at zone level to Tag management at account level](https://edgetunnel-b2h.pages.dev/_astro/zaraz-account-level.L5Bz9oN0_151oOs.webp) Previously, you could only configure Zaraz by going to each individual zone under your Cloudflare account. Now, if you’d like to get started with Zaraz or manage your existing configuration, you can navigate to the [Tag Management ↗](https://dash.cloudflare.com/?to=/:account/tag-management/zaraz) section on the Cloudflare dashboard – this will make it easier to compare and configure the same settings across multiple zones. These changes will not alter any existing configuration or entitlements for zones you already have Zaraz enabled on. If you’d like to edit existing configurations, you can go to the [Tag Setup ↗](https://dash.cloudflare.com/?to=/:account/tag-management/zaraz) section of the dashboard, and select the zone you'd like to edit. Feb 20, 2025 1. ### [Workers for Platforms - Instant dispatch for newly created User Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-20-synchronous-uploads/) [ Workers for Platforms ](https://edgetunnel-b2h.pages.dev/cloudflare-for-platforms/workers-for-platforms/) [Workers for Platforms ↗](https://edgetunnel-b2h.pages.dev/cloudflare-for-platforms/) is an architecture wherein a centralized [dispatch Worker](https://edgetunnel-b2h.pages.dev/cloudflare-for-platforms/workers-for-platforms/how-workers-for-platforms-works/#dynamic-dispatch-worker) processes incoming requests and routes them to isolated sub-Workers, called [User Workers](https://edgetunnel-b2h.pages.dev/cloudflare-for-platforms/workers-for-platforms/how-workers-for-platforms-works/#user-workers). ![Workers for Platforms Requests](https://edgetunnel-b2h.pages.dev/_astro/wfp-request.CZmZLaYf_Z2o8aKs.webp) Previously, when a new User Worker was uploaded, there was a short delay before it became available for dispatch. This meant that even though an API request could return a 200 OK response, the script might not yet be ready to handle requests, causing unexpected failures for platforms that immediately dispatch to new Workers. **With this update, first-time uploads of User Workers are now deployed synchronously**. A 200 OK response guarantees the script is fully provisioned and ready to handle traffic immediately, ensuring more predictable deployments and reducing errors. Feb 20, 2025 1. ### [Workers AI updated pricing](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-20-updated-pricing-docs/) [ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/) We've updated the Workers AI [pricing](https://edgetunnel-b2h.pages.dev/workers-ai/platform/pricing/) to include the latest models and how model usage maps to Neurons. * Each model's core input format(s) (tokens, audio seconds, images, etc) now include mappings to Neurons, making it easier to understand how your included Neuron volume is consumed and how you are charged at scale * Per-model pricing, instead of the previous bucket approach, allows us to be more flexible on how models are charged based on their size, performance and capabilities. As we optimize each model, we can then pass on savings for that model. * You will still only pay for what you consume: Workers AI inference is serverless, and not billed by the hour. Going forward, models will be launched with their associated Neuron costs, and we'll be updating the Workers AI dashboard and API to reflect consumption in both raw units and Neurons. Visit the [Workers AI pricing](https://edgetunnel-b2h.pages.dev/workers-ai/platform/pricing/) page to learn more about Workers AI pricing. Feb 20, 2025 1. ### [Autofix Worker name configuration errors at build time](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-20-builds-name-conflict/) [ Workers ](https://edgetunnel-b2h.pages.dev/workers/) ![Auto-fixing Workers Name in Git Repo](https://edgetunnel-b2h.pages.dev/_astro/gh-auto-pr-name.BHTtigEg_2smH.webp) Small misconfigurations shouldn’t break your deployments. Cloudflare is introducing automatic error detection and fixes in [Workers Builds](https://edgetunnel-b2h.pages.dev/workers/ci-cd/builds/), identifying common issues in your wrangler.toml or wrangler.jsonc and proactively offering fixes, so you spend less time debugging and more time shipping. Here's how it works: 1. Before running your build, Cloudflare checks your Worker's Wrangler configuration file (wrangler.toml or wrangler.jsonc) for common errors. 2. Once you submit a build, if Cloudflare finds an error it can fix, it will submit a pull request to your repository that fixes it. 3. Once you merge this pull request, Cloudflare will run another build. We're starting with fixing name mismatches between your Wrangler file and the Cloudflare dashboard, a top cause of build failures. This is just the beginning, we want your feedback on what other errors we should catch and fix next. Let us know in the Cloudflare Developers Discord, [#workers-and-pages-feature-suggestions ↗](https://discord.com/channels/595317990191398933/1064502845061210152). Feb 18, 2025 1. ### [WAF Release - 2025-02-18](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-18-waf-release/) [ WAF ](https://edgetunnel-b2h.pages.dev/waf/) | Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments | | -------------------------- | ----------- | -------------- | --------------------------------------------------- | --------------- | ---------- | ----------------------- | | Cloudflare Managed Ruleset | ...a2ffa4b8 | 100715 | FortiOS - Auth Bypass - CVE:CVE-2024-55591 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...5a883e12 | 100716 | Ivanti - Auth Bypass - CVE:CVE-2021-44529 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...958094d3 | 100717 | SimpleHelp - Auth Bypass - CVE:CVE-2024-57727 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...3b66df22 | 100718 | SonicWall SSLVPN - Auth Bypass - CVE:CVE-2024-53704 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...9184699f | 100719 | Yeti Platform - Auth Bypass - CVE:CVE-2024-46507 | Log | Block | This is a New Detection | Feb 14, 2025 1. ### [Customize queue message retention periods](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-14-customize-queue-retention-period/) [ Queues ](https://edgetunnel-b2h.pages.dev/queues/) You can now customize a queue's message retention period, from a minimum of 60 seconds to a maximum of 14 days. Previously, it was fixed to the default of 4 days. ![Customize a queue's message retention period](https://edgetunnel-b2h.pages.dev/_astro/customize-retention-period.CpK7s10q_19dmJh.webp) You can customize the retention period on the settings page for your queue, or using Wrangler: **Update message retention period** ```bash $ wrangler queues update my-queue --message-retention-period-secs 600 ``` This feature is available on all new and existing queues. If you haven't used Cloudflare Queues before, [get started with the Cloudflare Queues guide](https://edgetunnel-b2h.pages.dev/queues/get-started). Feb 14, 2025 1. ### [Build AI Agents with Example Prompts](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-14-example-ai-prompts/) [ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)[ Workflows ](https://edgetunnel-b2h.pages.dev/workflows/) We've added an [example prompt](https://edgetunnel-b2h.pages.dev/workers/get-started/prompting/) to help you get started with building AI agents and applications on Cloudflare [Workers](https://edgetunnel-b2h.pages.dev/workers/), including [Workflows](https://edgetunnel-b2h.pages.dev/workflows/), [Durable Objects](https://edgetunnel-b2h.pages.dev/durable-objects/), and [Workers KV](https://edgetunnel-b2h.pages.dev/kv/). You can use this prompt with your favorite AI model, including Claude 3.5 Sonnet, OpenAI's o3-mini, Gemini 2.0 Flash, or Llama 3.3 on Workers AI. Models with large context windows will allow you to paste the prompt directly: provide your own prompt within the `` tags. ```sh {paste_prompt_here} user: Build an AI agent using Cloudflare Workflows. The Workflow should run when a new GitHub issue is opened on a specific project with the label 'help' or 'bug', and attempt to help the user troubleshoot the issue by calling the OpenAI API with the issue title and description, and a clear, structured prompt that asks the model to suggest 1-3 possible solutions to the issue. Any code snippets should be formatted in Markdown code blocks. Documentation and sources should be referenced at the bottom of the response. The agent should then post the response to the GitHub issue. The agent should run as the provided GitHub bot account. ``` This prompt is still experimental, but we encourage you to try it out and [provide feedback ↗](https://github.com/cloudflare/cloudflare-docs/issues/new?template=content.edit.yml). Feb 14, 2025 1. ### [Configure your Magic WAN Connector to connect via static IP assignment](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-14-local-console-access/) [ Cloudflare One Appliance ](https://edgetunnel-b2h.pages.dev/cloudflare-wan/configuration/appliance/)[ Cloudflare One ](https://edgetunnel-b2h.pages.dev/cloudflare-one/)[ Cloudflare WAN ](https://edgetunnel-b2h.pages.dev/cloudflare-wan/) You can now locally configure your [Magic WAN Connector](https://edgetunnel-b2h.pages.dev/cloudflare-wan/configuration/appliance/) to work in a static IP configuration. This local method does not require having access to a DHCP Internet connection. However, it does require being comfortable with using tools to access the serial port on Magic WAN Connector as well as using a serial terminal client to access the Connector's environment. For more details, refer to [WAN with a static IP address](https://edgetunnel-b2h.pages.dev/cloudflare-wan/configuration/appliance/configure-hardware-appliance/#bootstrap-via-serial-console). Feb 14, 2025 1. ### [Super Slurper now transfers data to R2 up to 5x faster](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-14-r2-super-slurper-faster-migrations/) [ R2 ](https://edgetunnel-b2h.pages.dev/r2/) [Super Slurper](https://edgetunnel-b2h.pages.dev/r2/data-migration/super-slurper/) now transfers data from cloud object storage providers like AWS S3 and Google Cloud Storage to [Cloudflare R2](https://edgetunnel-b2h.pages.dev/r2/) up to 5x faster than it did before. We moved from a centralized service to a distributed system built on the Cloudflare Developer Platform — using [Cloudflare Workers](https://edgetunnel-b2h.pages.dev/workers/), [Durable Objects](https://edgetunnel-b2h.pages.dev/durable-objects/), and [Queues](https://edgetunnel-b2h.pages.dev/queues/) — to both improve performance and increase system concurrency capabilities (and we'll share more details about how we did it soon!) ![Super Slurper Objects Migrated](https://edgetunnel-b2h.pages.dev/_astro/slurper-objects-over-time-border.BFDkMQUw_KFpzV.webp) _Time to copy 75,000 objects from AWS S3 to R2 decreased from 15 minutes 30 seconds (old) to 3 minutes 25 seconds (after performance improvements)_ For more information on Super Slurper and how to migrate data from existing object storage to R2, refer to our [documentation](https://edgetunnel-b2h.pages.dev/r2/data-migration/super-slurper/). Feb 14, 2025 1. ### [Upload a certificate bundle with an RSA and ECDSA certificate per custom hostname](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-14-cert-bundling-for-custom-hostnames/) [ SSL/TLS ](https://edgetunnel-b2h.pages.dev/ssl/) Cloudflare has supported both RSA and ECDSA certificates across our platform for a number of years. Both certificates offer the same security, but ECDSA is more performant due to a smaller key size. However, RSA is more widely adopted and ensures compatibility with legacy clients. Instead of choosing between them, you may want both – that way, ECDSA is used when clients support it, but RSA is available if not. Now, you can upload both an RSA and ECDSA certificate on a custom hostname via the API. ```plaintext curl -X POST https://api.cloudflare.com/client/v4/zones/$ZONE_ID/custom_hostnames \ -H 'Content-Type: application/json' \ -H "X-Auth-Email: $CLOUDFLARE_EMAIL" \ -H "X-Auth-Key: $CLOUDFLARE_API_KEY" \ -d '{ "hostname": "hostname", "ssl": { "custom_cert_bundle": [ { "custom_certificate": "RSA Cert", "custom_key": "RSA Key" }, { "custom_certificate": "ECDSA Cert", "custom_key": "ECDSA Key" } ], "bundle_method": "force", "wildcard": false, "settings": { "min_tls_version": "1.0" } } }’ ``` You can also: * [Upload](https://edgetunnel-b2h.pages.dev/api/resources/custom%5Fhostnames/methods/create/) an RSA or ECDSA certificate to a custom hostname with an existing ECDSA or RSA certificate, respectively. * [Replace](https://edgetunnel-b2h.pages.dev/api/resources/custom%5Fhostnames/subresources/certificate%5Fpack/subresources/certificates/methods/update/) the RSA or ECDSA certificate with a certificate of its same type. * [Delete](https://edgetunnel-b2h.pages.dev/api/resources/custom%5Fhostnames/subresources/certificate%5Fpack/subresources/certificates/methods/delete/) the RSA or ECDSA certificate (if the custom hostname has both an RSA and ECDSA uploaded). This feature is available for Business and Enterprise customers who have purchased custom certificates. Feb 14, 2025 1. ### [Rewind, Replay, Resume: Introducing DVR for Stream Live](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-14-introducing-dvr-for-stream-live/) [ Stream ](https://edgetunnel-b2h.pages.dev/stream/) Previously, all viewers watched "the live edge," or the latest content of the broadcast, synchronously. If a viewer paused for more than a few seconds, the player would automatically "catch up" when playback started again. Seeking through the broadcast was only available once the recording was available after it concluded. Starting today, customers can make a small adjustment to the player embed or manifest URL to enable the DVR experience for their viewers. By offering this feature as an opt-in adjustment, our customers are empowered to pick the best experiences for their applications. When building a player embed code or manifest URL, just add `dvrEnabled=true` as a query parameter. There are some things to be aware of when using this option. For more information, refer to [DVR for Live](https://edgetunnel-b2h.pages.dev/stream/stream-live/dvr-for-live/). Feb 12, 2025 1. ### [Configurable multiplexing HTTP/2 to Origin](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-12-configurable-multiplexing-http2-to-origin/) [ Cache / CDN ](https://edgetunnel-b2h.pages.dev/cache/) You can now configure HTTP/2 multiplexing settings for origin connections on Enterprise plans. This feature allows you to optimize how Cloudflare manages concurrent requests over HTTP/2 connections to your origin servers, improving cache efficiency and reducing connection overhead. #### How it works HTTP/2 multiplexing allows multiple requests to be sent over a single TCP connection. With this configuration option, you can: 1. **Control concurrent streams**: Adjust the maximum number of concurrent streams per connection. 2. **Optimize connection reuse**: Fine-tune connection pooling behavior for your origin infrastructure. 3. **Reduce connection overhead**: Minimize the number of TCP connections required between Cloudflare and your origin. 4. **Improve cache performance**: Better connection management can enhance cache fetch efficiency. #### Benefits * **Customizable performance**: Tailor multiplexing settings to your origin's capabilities. * **Reduced latency**: Fewer connection handshakes improve response times. * **Lower origin load**: More efficient connection usage reduces server resource consumption. * **Enhanced scalability**: Better connection management supports higher traffic volumes. #### Get started Enterprise customers can configure HTTP/2 multiplexing settings in the [Cloudflare Dashboard ↗](https://dash.cloudflare.com/) or through our [API](https://edgetunnel-b2h.pages.dev/api/). Important consideration This setting needs to be tuned carefully for your origin infrastructure. Setting the concurrent stream limit too high can negatively impact performance by saturating the shared TCP connection and overwhelming server processing capacity, leading to increased latency for individual requests. Feb 12, 2025 1. ### [Increased Cloudflare Rules limits](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-12-rules-upgraded-limits/) [ Rules ](https://edgetunnel-b2h.pages.dev/rules/) We have upgraded and streamlined [Cloudflare Rules](https://edgetunnel-b2h.pages.dev/rules/) limits across all plans, simplifying rule management and improving scalability for everyone. **New limits by product:** * [Bulk Redirects](https://edgetunnel-b2h.pages.dev/rules/url-forwarding/bulk-redirects/) * Free: **20** → **10,000** URL redirects across lists * Pro: **500** → **25,000** URL redirects across lists * Business: **500** → **50,000** URL redirects across lists * Enterprise: **10,000** → **1,000,000** URL redirects across lists * [Cloud Connector](https://edgetunnel-b2h.pages.dev/rules/cloud-connector/) * Free: **5** → **10** connectors * Enterprise: **125** → **300** connectors * [Custom Errors](https://edgetunnel-b2h.pages.dev/rules/custom-errors/) * Pro: **5** → **25** error assets and rules * Business: **20** → **50** error assets and rules * Enterprise: **50** → **300** error assets and rules * [Snippets](https://edgetunnel-b2h.pages.dev/rules/snippets/) * Pro: **10** → **25** code snippets and rules * Business: **25** → **50** code snippets and rules * Enterprise: **50** → **300** code snippets and rules * [Cache Rules](https://edgetunnel-b2h.pages.dev/cache/how-to/cache-rules/), [Configuration Rules](https://edgetunnel-b2h.pages.dev/rules/configuration-rules/), [Compression Rules](https://edgetunnel-b2h.pages.dev/rules/compression-rules/), [Origin Rules](https://edgetunnel-b2h.pages.dev/rules/origin-rules/), [Single Redirects](https://edgetunnel-b2h.pages.dev/rules/url-forwarding/single-redirects/), and [Transform Rules](https://edgetunnel-b2h.pages.dev/rules/transform/) * Enterprise: **125** → **300** rules Gradual rollout Limits are updated gradually. Some customers may still see previous limits until the rollout is fully completed in the first half of 2025. Feb 11, 2025 1. ### [Custom Errors (beta): Stored Assets & Account-level Rules](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-11-custom-errors-beta/) [ Rules ](https://edgetunnel-b2h.pages.dev/rules/) We're introducing [Custom Errors](https://edgetunnel-b2h.pages.dev/rules/custom-errors/) (beta), which builds on our existing Custom Error Responses feature with new asset storage capabilities. This update allows you to store externally hosted error pages on Cloudflare and reference them in custom error rules, eliminating the need to supply inline content. This brings the following new capabilities: * **Custom error assets** – Fetch and store external error pages at the edge for use in error responses. * **Account-Level custom errors** – Define error handling rules and assets at the account level for consistency across multiple zones. Zone-level rules take precedence over account-level ones, and assets are not shared between levels. You can use Cloudflare API to upload your existing assets for use with Custom Errors: ```bash curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_pages/assets" \ --header "Authorization: Bearer " \ --header 'Content-Type: application/json' \ --data '{ "name": "maintenance", "description": "Maintenance template page", "url": "https://example.com/" }' ``` You can then reference the stored asset in a Custom Error rule: ```bash curl --request PUT \ "https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets/phases/http_custom_errors/entrypoint" \ --header "Authorization: Bearer " \ --header 'Content-Type: application/json' \ --data '{ "rules": [ { "action": "serve_error", "action_parameters": { "asset_name": "maintenance", "content_type": "text/html", "status_code": 503 }, "enabled": true, "expression": "http.request.uri.path contains \"error\"" } ] }' ``` Feb 11, 2025 1. ### [WAF Release - 2025-02-11](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-11-waf-release/) [ WAF ](https://edgetunnel-b2h.pages.dev/waf/) | Ruleset | Rule ID | Legacy Rule ID | Description | Previous Action | New Action | Comments | | -------------------------- | ----------- | -------------- | ------------------------------------------------------------------------- | --------------- | ---------- | ----------------------- | | Cloudflare Managed Ruleset | ...483b4c26 | 100708 | Aviatrix Network - Remote Code Execution - CVE:CVE-2024-50603 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...7e924ca3 | 100709 | Next.js - Remote Code Execution - CVE:CVE-2024-46982 | Log | Disabled | This is a New Detection | | Cloudflare Managed Ruleset | ...83a7d8ff | 100710 | Progress Software WhatsUp Gold - Directory Traversal - CVE:CVE-2024-12105 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...baa8eb34 | 100711 | WordPress - Remote Code Execution - CVE:CVE-2024-56064 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...87f5d34e | 100712 | WordPress - Remote Code Execution - CVE:CVE-2024-9047 | Log | Block | This is a New Detection | | Cloudflare Managed Ruleset | ...bf72cf8a | 100713 | FortiOS - Auth Bypass - CVE:CVE-2022-40684 | Log | Block | This is a New Detection | Feb 07, 2025 1. ### [Open email links with Security Center](https://edgetunnel-b2h.pages.dev/changelog/post/2025-02-07-open-links-security-center/) [ Email security ](https://edgetunnel-b2h.pages.dev/cloudflare-one/email-security/) You can now investigate links in emails with Cloudflare Security Center to generate a report containing a myriad of technical details: a phishing scan, SSL certificate data, HTTP request and response data, page performance data, DNS records, what technologies and libraries the page uses, and more. ![Open links in Security Center](https://edgetunnel-b2h.pages.dev/_astro/Open-Links-Security-Center.b-LJU4YB_2dBHq8.webp) From **Investigation**, go to **View details**, and look for the **Links identified** section. Select **Open in Security Center** next to each link. **Open in Security Center** allows your team to quickly generate a detailed report about the link with no risk to the analyst or your environment. For more details, refer to [Open links](https://edgetunnel-b2h.pages.dev/cloudflare-one/email-security/investigation/search-email/#open-links). This feature is available across these Email security packages: * **Advantage** * **Enterprise** * **Enterprise + PhishGuard** ```json {"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/40/#page","headline":"Changelogs | Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/changelog/40/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/cf-twitter-card.png","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}} ```