mirror of
https://github.com/cloudflare/cloudflare-docs.git
synced 2026-01-16 23:11:06 +00:00
[Chore] Remove timestamps from changelogs (#23678)
* [Chore] Remove timestamps from changelogs * update * style guide tweak * update test
This commit is contained in:
Kody Jackson
GitHub
parent
a351077e31
commit
3be4881387
191 changed files with 512 additions and 504 deletions
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Eliminate long-lived credentials and enhance SSH security with Cloudflare Access for Infrastructure
|
||||
description: Use short-lived SSH certificates and fine-grained policy to secure access to your SSH servers.
|
||||
date: 2024-10-01T6:00:00Z
|
||||
date: 2024-10-01
|
||||
---
|
||||
|
||||
Organizations can now eliminate long-lived credentials from their SSH setup and enable strong multi-factor authentication for SSH access, similar to other Access applications, all while generating access and command logs.
|
||||
|
|
@ -9,6 +9,7 @@ Organizations can now eliminate long-lived credentials from their SSH setup and
|
|||
SSH with [Access for Infrastructure](/cloudflare-one/applications/non-http/infrastructure-apps/) uses short-lived SSH certificates from Cloudflare, eliminating SSH key management and reducing the security risks associated with lost or stolen keys. It also leverages a common deployment model for Cloudflare One customers: [WARP-to-Tunnel](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-warp-to-tunnel/).
|
||||
|
||||
SSH with Access for Infrastructure enables you to:
|
||||
|
||||
- **Author fine-grained policy** to control who may access your SSH servers, including specific ports, protocols, and SSH users.
|
||||
- **Monitor infrastructure access** with Access and SSH command logs, supporting regulatory compliance and providing visibility in case of security breach.
|
||||
- **Preserve your end users' workflows.** SSH with Access for Infrastructure supports native SSH clients and does not require any modifications to users’ SSH configs.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Export SSH command logs with Access for Infrastructure using Logpush
|
||||
description: Easily configure automatic export of SSH command logs to third-party storage destinations or to security information and event management (SIEM) tools.
|
||||
date: 2025-01-15T6:00:00Z
|
||||
date: 2025-01-15
|
||||
---
|
||||
|
||||
:::note[Availability]
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: New SAML and OIDC Fields and SAML transforms for Access for SaaS
|
||||
description: Access for SaaS new SAML and OIDC Fields and SAML transforms
|
||||
date: 2025-03-03T6:00:00Z
|
||||
date: 2025-03-03
|
||||
---
|
||||
|
||||
[Access for SaaS applications](/cloudflare-one/applications/configure-apps/saas-apps/) now include more configuration options to support a wider array of SaaS applications.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Cloudflare Zero Trust SCIM User and Group Provisioning Logs
|
||||
description: View all user and group updates, creation and deletion events made via SCIM across all of your IdP instances in one place
|
||||
date: 2025-04-09T6:00:00Z
|
||||
date: 2025-04-09
|
||||
---
|
||||
|
||||
[Cloudflare Zero Trust SCIM provisioning](/cloudflare-one/identity/users/scim) now has a full audit log of all create, update and delete event from any SCIM Enabled IdP. The [SCIM logs](/cloudflare-one/insights/logs/scim-logs/) support filtering by IdP, Event type, Result and many more fields. This will help with debugging user and group update issues and questions.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,9 @@
|
|||
---
|
||||
title: Access bulk policy tester
|
||||
description: Test and simulate Access policies before deploying them to production. The Access bulk policy tester allows you to test your policies against your entire user population before and after deploying them.
|
||||
date: 2025-04-21T6:00:00Z
|
||||
date: 2025-04-21
|
||||
---
|
||||
|
||||
The [Access bulk policy tester](/cloudflare-one/policies/access/policy-management/#test-all-policies-in-an-application) is now available in the Cloudflare Zero Trust dashboard. The bulk policy tester allows you to simulate Access policies against your entire user base before and after deploying any changes. The policy tester will simulate the configured policy against each user's last seen identity and device posture (if applicable).
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,13 @@
|
|||
---
|
||||
title: Access RDP securely from your browser — now in open beta
|
||||
description: Connect to internal Windows servers via a web browser — no VPN or RDP client required.
|
||||
date: 2025-07-01T13:00:00Z
|
||||
date: 2025-07-01
|
||||
---
|
||||
|
||||
[Browser-based RDP](/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser/) with [Cloudflare Access](/cloudflare-one/policies/access/) is now available in open beta for all Cloudflare customers. It enables secure, remote Windows server access without VPNs or RDP clients.
|
||||
|
||||
With browser-based RDP, you can:
|
||||
|
||||
- **Control how users authenticate to internal RDP resources** with single sign-on (SSO), multi-factor authentication (MFA), and granular access policies.
|
||||
- **Record who is accessing which servers and when** to support regulatory compliance requirements and to gain greater visibility in the event of a security event.
|
||||
- **Eliminate the need to install and manage software on user devices**. You will only need a web browser.
|
||||
|
|
@ -15,4 +16,3 @@ With browser-based RDP, you can:
|
|||
|
||||
|
||||
To get started, see [Connect to RDP in a browser](/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser/).
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ products:
|
|||
- agents
|
||||
- workers
|
||||
- workflows
|
||||
date: 2025-02-14T19:00:00Z
|
||||
date: 2025-02-14
|
||||
---
|
||||
|
||||
We've added an [example prompt](/workers/get-started/prompting/) to help you get started with building AI agents and applications on Cloudflare [Workers](/workers/), including [Workflows](/workflows/), [Durable Objects](/durable-objects/), and [Workers KV](/kv/).
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: Build and ship AI Agents on Cloudflare using the Agents SDK
|
|||
products:
|
||||
- agents
|
||||
- workers
|
||||
date: 2025-02-25T14:00:00Z
|
||||
date: 2025-02-25
|
||||
---
|
||||
|
||||
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.
|
||||
|
|
@ -25,7 +25,7 @@ npm i agents
|
|||
... and then define your first Agent:
|
||||
|
||||
```ts
|
||||
import { Agent } from 'agents';
|
||||
import { Agent } from "agents";
|
||||
|
||||
export class YourAgent extends Agent<Env> {
|
||||
// Build it out
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: Install the latest version of the `agents` SDK to build multi-agent
|
|||
products:
|
||||
- agents
|
||||
- workers
|
||||
date: 2025-03-18T14:00:00Z
|
||||
date: 2025-03-18
|
||||
---
|
||||
|
||||
import { Badge, MetaInfo, Render, TypeScriptExample } from "~/components"
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: The Agents SDK now includes built-in support for building remote MC
|
|||
products:
|
||||
- agents
|
||||
- workers
|
||||
date: 2025-04-07T13:00:00Z
|
||||
date: 2025-04-07
|
||||
---
|
||||
|
||||
import { Render, PackageManagers, TypeScriptExample } from "~/components";
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ products:
|
|||
- agents
|
||||
- workers
|
||||
- workflows
|
||||
date: 2025-06-25T15:00:00Z
|
||||
date: 2025-06-25
|
||||
---
|
||||
|
||||
AI is supercharging app development for everyone, but we need a safe way to run untrusted, LLM-written code. We’re introducing [Sandboxes](https://www.npmjs.com/package/@cloudflare/sandbox), which let your Worker run actual processes in a secure, container-based environment.
|
||||
|
|
@ -15,10 +15,10 @@ import { getSandbox } from "@cloudflare/sandbox";
|
|||
export { Sandbox } from "@cloudflare/sandbox";
|
||||
|
||||
export default {
|
||||
async fetch(request: Request, env: Env) {
|
||||
const sandbox = getSandbox(env.Sandbox, "my-sandbox");
|
||||
return sandbox.exec("ls", ["-la"]);
|
||||
},
|
||||
async fetch(request: Request, env: Env) {
|
||||
const sandbox = getSandbox(env.Sandbox, "my-sandbox");
|
||||
return sandbox.exec("ls", ["-la"]);
|
||||
},
|
||||
};
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: AI Audit
|
||||
description: AI Audit is available to all customers
|
||||
date: 2024-09-23T11:00:00Z
|
||||
date: 2024-09-23
|
||||
---
|
||||
|
||||
Every site on Cloudflare now has access to [**AI Audit**](/ai-audit/), which summarizes the crawling behavior of popular and known AI services.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Introducing Pay Per Crawl (private beta)
|
||||
description: A new feature which allows site owners to charge crawlers for access to their content
|
||||
date: 2025-07-01T12:00:00Z
|
||||
date: 2025-07-01
|
||||
---
|
||||
|
||||
We are introducing a new feature of [AI Audit](/ai-audit/) — Pay Per Crawl. [Pay Per Crawl](/ai-audit/features/pay-per-crawl/what-is-pay-per-crawl/) enables site owners to require payment from AI crawlers every time the crawlers access their content, thereby fostering a fairer Internet by enabling site owners to control and monetize how their content gets used by AI.
|
||||
|
|
@ -9,11 +9,13 @@ We are introducing a new feature of [AI Audit](/ai-audit/) — Pay Per Crawl. [P
|
|||
|
||||
|
||||
**For Site Owners:**
|
||||
|
||||
- Set pricing and select which crawlers to charge for content access
|
||||
- Manage payments via Stripe
|
||||
- Monitor analytics on successful content deliveries
|
||||
|
||||
**For AI Crawler Owners:**
|
||||
|
||||
- Use HTTP headers to request and accept pricing
|
||||
- Receive clear confirmations on charges for accessed content
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: AI Audit refresh
|
||||
description: More intuitive AI crawler management
|
||||
date: 2025-07-01T11:00:00Z
|
||||
date: 2025-07-01
|
||||
---
|
||||
|
||||
We redesigned the AI Audit dashboard to provide more intuitive and granular control over AI crawlers.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: AI Gateway adds DeepSeek as a Provider
|
|||
description: AI Gateway has added DeepSeek as a new provider.
|
||||
products:
|
||||
- ai-gateway
|
||||
date: 2025-01-02T11:00:00Z
|
||||
date: 2025-01-02
|
||||
---
|
||||
|
||||
[**AI Gateway**](/ai-gateway/) now supports [**DeepSeek**](/ai-gateway/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](/workers-ai/), AI Gateway empowers you to:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: AI Gateway Introduces New Worker Binding Methods
|
|||
description: New Worker binding methods, enhancing integration capabilities for developers.
|
||||
products:
|
||||
- ai-gateway
|
||||
date: 2025-01-30T14:00:00Z
|
||||
date: 2025-01-30
|
||||
---
|
||||
|
||||
We have released new [Workers bindings API methods](/ai-gateway/integrations/worker-binding-methods/), allowing you to connect Workers applications to AI Gateway directly. These methods simplify how Workers calls AI services behind your AI Gateway configurations, removing the need to use the REST API and manually authenticate.
|
||||
|
|
|
|||
|
|
@ -3,12 +3,12 @@ title: AI Gateway adds Cerebras, ElevenLabs, and Cartesia as new providers
|
|||
description: AI Gateway has added Cerebras, ElevenLabs, and Cartesia as new providers.
|
||||
products:
|
||||
- ai-gateway
|
||||
date: 2025-02-05T12:00:00Z
|
||||
date: 2025-02-05
|
||||
---
|
||||
|
||||
[AI Gateway](/ai-gateway/) has added three new providers: [Cartesia](/ai-gateway/providers/cartesia/), [Cerebras](/ai-gateway/providers/cerebras/), and [ElevenLabs](/ai-gateway/providers/elevenlabs/), giving you more even more options for providers you can use through AI Gateway. Here's a brief overview of each:
|
||||
|
||||
- [Cartesia](/ai-gateway/providers/cartesia/) provides text-to-speech models that produce natural-sounding speech with low latency.
|
||||
- [Cartesia](/ai-gateway/providers/cartesia/) provides text-to-speech models that produce natural-sounding speech with low latency.
|
||||
- [Cerebras](/ai-gateway/providers/cerebras/) delivers low-latency AI inference to Meta's Llama 3.1 8B and Llama 3.3 70B models.
|
||||
- [ElevenLabs](/ai-gateway/providers/elevenlabs/) offers text-to-speech models with human-like voices in 32 languages.
|
||||
|
||||
|
|
@ -30,4 +30,3 @@ curl -X POST https://gateway.ai.cloudflare.com/v1/ACCOUNT_TAG/GATEWAY/cerebras/c
|
|||
]
|
||||
}'
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Request timeouts and retries with AI Gateway
|
|||
description: AI Gateway has added additional request handling, with request timeouts and request retries
|
||||
products:
|
||||
- ai-gateway
|
||||
date: 2025-02-06T11:00:00Z
|
||||
date: 2025-02-06
|
||||
---
|
||||
|
||||
AI Gateway adds additional ways to handle requests - [Request Timeouts](/ai-gateway/configuration/request-handling/#request-timeouts) and [Request Retries](/ai-gateway/configuration/request-handling/#request-retries), making it easier to keep your applications responsive and reliable.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Introducing Guardrails in AI Gateway
|
||||
description: Keep AI interactions secure and risk-free with Guardrails in AI Gateway
|
||||
date: 2025-02-26T6:00:00Z
|
||||
date: 2025-02-26
|
||||
preview_image: ~/assets/images/changelog/ai-gateway/guardrails-social-preview.png
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: AI Gateway launches Realtime WebSockets API
|
||||
description: AI Gateway now supports end-to-end, client-to-provider WebSockets
|
||||
date: 2025-03-21T09:00:00Z
|
||||
date: 2025-03-21
|
||||
---
|
||||
|
||||
We are excited to announce that [AI Gateway](/ai-gateway/) now supports real-time AI interactions with the new [Realtime WebSockets API](/ai-gateway/websockets-api/realtime-api/).
|
||||
|
|
|
|||
|
|
@ -3,28 +3,29 @@ title: AI Gateway adds OpenAI compatible endpoint
|
|||
description: AI Gateway has added OpenAI compatibility
|
||||
products:
|
||||
- ai-gateway
|
||||
date: 2025-06-03T12:00:00Z
|
||||
date: 2025-06-03
|
||||
---
|
||||
Users can now use an [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) in AI Gateway to easily switch between providers, while keeping the exact same request and response formats. We're launching now with the chat completions endpoint, with the embeddings endpoint coming up next.
|
||||
|
||||
Users can now use an [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) in AI Gateway to easily switch between providers, while keeping the exact same request and response formats. We're launching now with the chat completions endpoint, with the embeddings endpoint coming up next.
|
||||
|
||||
To get started, use the OpenAI compatible chat completions endpoint URL with your own account id and gateway id and switch between providers by changing the `model` and `apiKey` parameters.
|
||||
|
||||
```js title="OpenAI SDK Example"
|
||||
import OpenAI from "openai";
|
||||
const client = new OpenAI({
|
||||
apiKey: "YOUR_PROVIDER_API_KEY", // Provider API key
|
||||
baseURL:
|
||||
"https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat",
|
||||
apiKey: "YOUR_PROVIDER_API_KEY", // Provider API key
|
||||
baseURL:
|
||||
"https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat",
|
||||
});
|
||||
|
||||
const response = await client.chat.completions.create({
|
||||
model: "google-ai-studio/gemini-2.0-flash",
|
||||
messages: [{ role: "user", content: "What is Cloudflare?" }],
|
||||
model: "google-ai-studio/gemini-2.0-flash",
|
||||
messages: [{ role: "user", content: "What is Cloudflare?" }],
|
||||
});
|
||||
|
||||
console.log(response.choices[0].message.content);
|
||||
```
|
||||
|
||||
Additionally, the [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) can be combined with our [Universal Endpoint](/ai-gateway/universal/) to add fallbacks across multiple providers. That means AI Gateway will return every response in the same standardized format, no extra parsing logic required!
|
||||
Additionally, the [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) can be combined with our [Universal Endpoint](/ai-gateway/universal/) to add fallbacks across multiple providers. That means AI Gateway will return every response in the same standardized format, no extra parsing logic required!
|
||||
|
||||
Learn more in the [OpenAI Compatibility](/ai-gateway/chat-completion/) documentation.
|
||||
Learn more in the [OpenAI Compatibility](/ai-gateway/chat-completion/) documentation.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: New GraphQL Analytics API Explorer and MCP Server
|
||||
description: Easily explore, build, and run GraphQL queries with two new tools
|
||||
date: 2025-05-23T11:00:00Z
|
||||
date: 2025-05-23
|
||||
---
|
||||
|
||||
We’ve launched two powerful new tools to make the GraphQL Analytics API more accessible:
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: New API Posture Management for API Shield
|
||||
description: Monitor for API-specific threats and risks with Posture Management for API Shield
|
||||
date: 2025-03-18T11:00:00Z
|
||||
date: 2025-03-18
|
||||
---
|
||||
|
||||
Now, API Shield **automatically** labels your API inventory with API-specific risks so that you can track and manage risks to your APIs.
|
||||
|
|
@ -10,14 +10,14 @@ View these risks in [Endpoint Management](/api-shield/management-and-monitoring/
|
|||
|
||||
|
||||
|
||||
...or in [Security Center Insights](/security-center/security-insights/):
|
||||
...or in [Security Center Insights](/security-center/security-insights/):
|
||||
|
||||
|
||||
|
||||
|
||||
API Shield will scan for risks on your API inventory daily. Here are the new risks we're scanning for and automatically labelling:
|
||||
|
||||
- **cf-risk-sensitive**: applied if the customer is subscribed to the [sensitive data detection ruleset](/waf/managed-rules/reference/sensitive-data-detection/) and the WAF detects sensitive data returned on an endpoint in the last seven days.
|
||||
- **cf-risk-missing-auth**: applied if the customer has configured a session ID and no successful requests to the endpoint contain the session ID.
|
||||
- **cf-risk-missing-auth**: applied if the customer has configured a session ID and no successful requests to the endpoint contain the session ID.
|
||||
- **cf-risk-mixed-auth**: applied if the customer has configured a session ID and some successful requests to the endpoint contain the session ID while some lack the session ID.
|
||||
- **cf-risk-missing-schema**: added when a learned schema is available for an endpoint that has no active schema.
|
||||
- **cf-risk-error-anomaly**: added when an endpoint experiences a recent increase in response errors over the last 24 hours.
|
||||
|
|
@ -25,9 +25,9 @@ API Shield will scan for risks on your API inventory daily. Here are the new ris
|
|||
- **cf-risk-size-anomaly**: added when an endpoint experiences a spike in response body size over the last 24 hours.
|
||||
|
||||
In addition, API Shield has two new 'beta' scans for **Broken Object Level Authorization (BOLA) attacks**. If you're in the beta, you will see the following two labels when API Shield suspects an endpoint is suffering from a BOLA vulnerability:
|
||||
|
||||
- **cf-risk-bola-enumeration**: added when an endpoint experiences successful responses with drastic differences in the number of unique elements requested by different user sessions.
|
||||
- **cf-risk-bola-pollution**: added when an endpoint experiences successful responses where parameters are found in multiple places in the request.
|
||||
|
||||
- **cf-risk-bola-enumeration**: added when an endpoint experiences successful responses with drastic differences in the number of unique elements requested by different user sessions.
|
||||
- **cf-risk-bola-pollution**: added when an endpoint experiences successful responses where parameters are found in multiple places in the request.
|
||||
|
||||
We are currently accepting more customers into our beta. Contact your account team if you are interested in BOLA attack detection for your API.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Audit logs (version 2) - Beta Release
|
||||
description: New version of audit logs
|
||||
date: 2025-03-27T11:00:00Z
|
||||
date: 2025-03-27
|
||||
---
|
||||
The latest version of audit logs streamlines audit logging by automatically capturing all user and system actions performed through the Cloudflare Dashboard or public APIs. This update leverages Cloudflare’s existing API Shield to generate audit logs based on OpenAPI schemas, ensuring a more consistent and automated logging process.
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ Use the following API endpoint to retrieve audit logs:
|
|||
GET https://api.cloudflare.com/client/v4/accounts/<account_id>/logs/audit?since=<date>&before=<date>
|
||||
|
||||
```
|
||||
You can access detailed documentation for audit logs (version 2) Beta API release [here](https://developers.cloudflare.com/api/resources/accounts/subresources/logs/subresources/audit/methods/list/).
|
||||
You can access detailed documentation for audit logs (version 2) Beta API release [here](https://developers.cloudflare.com/api/resources/accounts/subresources/logs/subresources/audit/methods/list/).
|
||||
|
||||
**Key Improvements in the Beta Release:**
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: AutoRAG lets you create fully-managed, retrieval-augmented generati
|
|||
products:
|
||||
- autorag
|
||||
- vectorize
|
||||
date: 2025-04-07T6:00:00Z
|
||||
date: 2025-04-07
|
||||
---
|
||||
|
||||
[AutoRAG](/autorag) is now in open beta, making it easy for you to build fully-managed retrieval-augmented generation (RAG) pipelines without managing infrastructure. Just upload your docs to [R2](/r2/get-started/), and AutoRAG handles the rest: embeddings, indexing, retrieval, and response generation via API.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Metadata filtering and multitenancy support in AutoRAG
|
|||
description: Add metadata filters to AutoRAG queries to enable multitenancy and control the scope of retrieved results.
|
||||
products:
|
||||
- autorag
|
||||
date: 2025-04-23T6:00:00Z
|
||||
date: 2025-04-23
|
||||
---
|
||||
|
||||
You can now filter [AutoRAG](/autorag) search results by `folder` and `timestamp` using [metadata filtering](/autorag/configuration/metadata) to narrow down the scope of your query.
|
||||
|
|
|
|||
|
|
@ -3,12 +3,12 @@ title: View custom metadata in responses and guide AI-search with context in Aut
|
|||
description: You can now view custom metadata in AutoRAG search responses and use a context field to provide additional guidance to AI-generated answers.
|
||||
products:
|
||||
- autorag
|
||||
date: 2025-06-19T6:10:00Z
|
||||
date: 2025-06-19
|
||||
---
|
||||
|
||||
In [AutoRAG](/autorag/), you can now view your object's custom metadata in the response from [`/search`](/autorag/usage/workers-binding/) and [`/ai-search`](/autorag/usage/workers-binding/), and optionally add a `context` field in the custom metadata of an object to provide additional guidance for AI-generated answers.
|
||||
|
||||
You can add [custom metadata](/r2/api/workers/workers-api-reference/#r2putoptions) to an object when uploading it to your R2 bucket.
|
||||
You can add [custom metadata](/r2/api/workers/workers-api-reference/#r2putoptions) to an object when uploading it to your R2 bucket.
|
||||
|
||||
# Object's custom metadata in search responses
|
||||
|
||||
|
|
@ -18,15 +18,15 @@ For example, the `attributes` section of your search response may look like:
|
|||
|
||||
```json
|
||||
{
|
||||
"attributes": {
|
||||
"timestamp": 1750001460000,
|
||||
"folder": "docs/",
|
||||
"filename": "launch-checklist.md",
|
||||
"file": {
|
||||
"url": "https://wiki.company.com/docs/launch-checklist",
|
||||
"context": "A checklist for internal launch readiness, including legal, engineering, and marketing steps."
|
||||
}
|
||||
}
|
||||
"attributes": {
|
||||
"timestamp": 1750001460000,
|
||||
"folder": "docs/",
|
||||
"filename": "launch-checklist.md",
|
||||
"file": {
|
||||
"url": "https://wiki.company.com/docs/launch-checklist",
|
||||
"context": "A checklist for internal launch readiness, including legal, engineering, and marketing steps."
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
|
@ -40,10 +40,10 @@ For example:
|
|||
|
||||
```json
|
||||
{
|
||||
"context": "summary: 'Checklist for internal product launch readiness, including legal, engineering, and marketing steps.'; url: 'https://wiki.company.com/docs/launch-checklist'"
|
||||
"context": "summary: 'Checklist for internal product launch readiness, including legal, engineering, and marketing steps.'; url: 'https://wiki.company.com/docs/launch-checklist'"
|
||||
}
|
||||
```
|
||||
|
||||
This gives you more control over how your content is interpreted, without requiring you to modify the original contents of the file.
|
||||
|
||||
Learn more in AutoRAG's [metadata filtering documentation](/autorag/configuration/metadata).
|
||||
Learn more in AutoRAG's [metadata filtering documentation](/autorag/configuration/metadata).
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
---
|
||||
title: Filter your AutoRAG search by file name
|
||||
description: You can now filter AutoRAG search queries by file name, allowing you to control which files can be retrieved for a given query.
|
||||
title: Filter your AutoRAG search by file name
|
||||
description: You can now filter AutoRAG search queries by file name, allowing you to control which files can be retrieved for a given query.
|
||||
products:
|
||||
- autorag
|
||||
date: 2025-06-19T6:00:00Z
|
||||
date: 2025-06-19
|
||||
---
|
||||
|
||||
In [AutoRAG](/autorag/), you can now [filter](/autorag/configuration/metadata/) by an object's file name using the `filename` attribute, giving you more control over which files are searched for a given query.
|
||||
|
|
@ -14,15 +14,15 @@ For example, your search query may look like:
|
|||
|
||||
```js
|
||||
const response = await env.AI.autorag("my-autorag").search({
|
||||
query: "what is the project deadline?",
|
||||
filters: {
|
||||
type: "eq",
|
||||
key: "filename",
|
||||
value: "project-alpha-roadmap.md",
|
||||
},
|
||||
query: "what is the project deadline?",
|
||||
filters: {
|
||||
type: "eq",
|
||||
key: "filename",
|
||||
value: "project-alpha-roadmap.md",
|
||||
},
|
||||
});
|
||||
```
|
||||
|
||||
This allows you to connect your application logic with AutoRAG's retrieval process, making it easy to control what gets searched without needing to reindex or modify your data.
|
||||
|
||||
Learn more in AutoRAG's [metadata filtering documentation](/autorag/configuration/metadata/).
|
||||
Learn more in AutoRAG's [metadata filtering documentation](/autorag/configuration/metadata/).
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@ title: Faster indexing and new Jobs view in AutoRAG
|
|||
description: Track your indexing pipeline in real time with 3–5× faster indexing and a new Jobs dashboard.
|
||||
products:
|
||||
- autorag
|
||||
date: 2025-07-08T6:00:00Z
|
||||
date: 2025-07-08
|
||||
---
|
||||
|
||||
You can now expect **3-5× faster indexing** in AutoRAG, and with it, a brand new **Jobs view** to help you monitor indexing progress.
|
||||
You can now expect **3-5× faster indexing** in AutoRAG, and with it, a brand new **Jobs view** to help you monitor indexing progress.
|
||||
|
||||
With each AutoRAG, indexing jobs are automatically triggered to sync your data source (i.e. R2 bucket) with your Vectorize index, ensuring new or updated files are reflected in your query results. You can also trigger jobs manually via the [Sync API](/api/resources/autorag/subresources/rags/) or by clicking “Sync index” in the dashboard.
|
||||
|
||||
|
|
@ -18,8 +18,8 @@ With the new jobs observability, you can now:
|
|||
|
||||
|
||||
|
||||
This makes it easier to understand what’s happening behind the scenes.
|
||||
This makes it easier to understand what’s happening behind the scenes.
|
||||
|
||||
**Coming soon:** We’re adding APIs to programmatically check indexing status, making it even easier to integrate AutoRAG into your workflows.
|
||||
|
||||
Try it out today on the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/ai/autorag).
|
||||
Try it out today on the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/ai/autorag).
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Gain visibility into user actions in Zero Trust Browser Isolation sessions
|
||||
description: User action logs for Remote Browser Isolation
|
||||
date: 2025-03-04T11:00:00Z
|
||||
date: 2025-03-04
|
||||
---
|
||||
|
||||
We're excited to announce that new logging capabilities for [Remote Browser Isolation (RBI)](/cloudflare-one/policies/browser-isolation/) through [Logpush](/logs/reference/log-fields/account/) are available in Beta starting today!
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: Browser Rendering now supports more concurrent browser sessions.
|
|||
products:
|
||||
- workers
|
||||
- browser-rendering
|
||||
date: 2025-01-30T13:00:00Z
|
||||
date: 2025-01-30
|
||||
---
|
||||
|
||||
import { Render, PackageManagers, TypeScriptExample } from "~/components"
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: New REST API is in open beta!
|
|||
description: We've released a new REST API in open beta.
|
||||
products:
|
||||
- browser-rendering
|
||||
date: 2025-02-27T12:00:00Z
|
||||
date: 2025-02-27
|
||||
---
|
||||
|
||||
We've released a new REST API for [Browser Rendering](/browser-rendering/) in open beta, making interacting with browsers easier than ever. This new API provides endpoints for common browser actions, with more to be added in the future.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Playwright for Browser Rendering now available
|
|||
description: Developers can now use the Playwright library for browser automation with Browser Rendering
|
||||
products:
|
||||
- browser-rendering
|
||||
date: 2025-04-04T14:00:00Z
|
||||
date: 2025-04-04
|
||||
---
|
||||
|
||||
We're excited to share that you can now use Playwright's browser automation [capabilities](https://playwright.dev/docs/api/class-playwright) from Cloudflare [Workers](/workers/).
|
||||
|
|
@ -13,39 +13,40 @@ We're excited to share that you can now use Playwright's browser automation [cap
|
|||
Below is an example of how to use Playwright with Browser Rendering to test a TODO application using assertions:
|
||||
|
||||
```ts title="Assertion example"
|
||||
import { launch, type BrowserWorker } from '@cloudflare/playwright';
|
||||
import { expect } from '@cloudflare/playwright/test';
|
||||
import { launch, type BrowserWorker } from "@cloudflare/playwright";
|
||||
import { expect } from "@cloudflare/playwright/test";
|
||||
|
||||
interface Env {
|
||||
MYBROWSER: BrowserWorker;
|
||||
MYBROWSER: BrowserWorker;
|
||||
}
|
||||
|
||||
export default {
|
||||
async fetch(request: Request, env: Env) {
|
||||
async fetch(request: Request, env: Env) {
|
||||
const browser = await launch(env.MYBROWSER);
|
||||
const page = await browser.newPage();
|
||||
|
||||
const browser = await launch(env.MYBROWSER);
|
||||
const page = await browser.newPage();
|
||||
await page.goto("https://demo.playwright.dev/todomvc");
|
||||
|
||||
await page.goto('https://demo.playwright.dev/todomvc');
|
||||
const TODO_ITEMS = [
|
||||
"buy some cheese",
|
||||
"feed the cat",
|
||||
"book a doctors appointment",
|
||||
];
|
||||
|
||||
const TODO_ITEMS = [
|
||||
'buy some cheese',
|
||||
'feed the cat',
|
||||
'book a doctors appointment'
|
||||
];
|
||||
const newTodo = page.getByPlaceholder("What needs to be done?");
|
||||
for (const item of TODO_ITEMS) {
|
||||
await newTodo.fill(item);
|
||||
await newTodo.press("Enter");
|
||||
}
|
||||
|
||||
const newTodo = page.getByPlaceholder('What needs to be done?');
|
||||
for (const item of TODO_ITEMS) {
|
||||
await newTodo.fill(item);
|
||||
await newTodo.press('Enter');
|
||||
}
|
||||
await expect(page.getByTestId("todo-title")).toHaveCount(TODO_ITEMS.length);
|
||||
|
||||
await expect(page.getByTestId('todo-title')).toHaveCount(TODO_ITEMS.length);
|
||||
|
||||
await Promise.all(TODO_ITEMS.map(
|
||||
(value, index) => expect(page.getByTestId('todo-title').nth(index)).toHaveText(value)
|
||||
));
|
||||
},
|
||||
await Promise.all(
|
||||
TODO_ITEMS.map((value, index) =>
|
||||
expect(page.getByTestId("todo-title").nth(index)).toHaveText(value),
|
||||
),
|
||||
);
|
||||
},
|
||||
};
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Browser Rendering REST API is Generally Available, with new endpoints and
|
|||
description: Browser Rendering updates - free tier and REST API GA with new endpoints
|
||||
products:
|
||||
- browser-rendering
|
||||
date: 2025-04-07T6:00:00Z
|
||||
date: 2025-04-07
|
||||
---
|
||||
|
||||
We’re excited to announce Browser Rendering is now available on the [Workers Free plan](https://www.cloudflare.com/plans/developer-platform/), making it even easier to prototype and experiment with web search and headless browser use-cases when building applications on Workers.
|
||||
|
|
|
|||
|
|
@ -3,12 +3,10 @@ title: Playwright MCP server is now compatible with Browser Rendering
|
|||
description: You can now deploy Playwright MCP and use any MCP client to get AI models to interact with Browser Rendering
|
||||
products:
|
||||
- browser-rendering
|
||||
date: 2025-05-28T08:00:00Z
|
||||
date: 2025-05-28
|
||||
---
|
||||
|
||||
import {
|
||||
PackageManagers,
|
||||
} from "~/components";
|
||||
import { PackageManagers } from "~/components";
|
||||
|
||||
We're excited to share that you can now use the [Playwright MCP](https://github.com/cloudflare/playwright-mcp) server with Browser Rendering.
|
||||
|
||||
|
|
@ -23,11 +21,11 @@ Playwright MCP is available as an npm package at [`@cloudflare/playwright-mcp`](
|
|||
Deploying the server is then as easy as:
|
||||
|
||||
```ts
|
||||
import { env } from 'cloudflare:workers';
|
||||
import { createMcpAgent } from '@cloudflare/playwright-mcp';
|
||||
import { env } from "cloudflare:workers";
|
||||
import { createMcpAgent } from "@cloudflare/playwright-mcp";
|
||||
|
||||
export const PlaywrightMCP = createMcpAgent(env.BROWSER);
|
||||
export default PlaywrightMCP.mount('/sse');
|
||||
export default PlaywrightMCP.mount("/sse");
|
||||
```
|
||||
|
||||
Check out the full code at [GitHub](https://github.com/cloudflare/playwright-mcp).
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Fight CSAM More Easily Than Ever
|
|||
description: Simplified setup for Cloudflare's CSAM Scanning Tool, improving child safety protections for websites.
|
||||
products:
|
||||
- cache
|
||||
date: 2025-02-04T12:00:00Z
|
||||
date: 2025-02-04
|
||||
---
|
||||
|
||||
You can now implement our **child safety tooling**, the **[CSAM Scanning Tool](/cache/reference/csam-scanning/)**, more easily. Instead of requiring external reporting credentials, you only need a verified email address for notifications to onboard. This change makes the tool more accessible to a wider range of customers.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,19 @@
|
|||
---
|
||||
title: All cache purge methods now available for all plans
|
||||
description: All Cloudflare plans can purge by tag, prefix, url, host, or everything to invalidate cached content on the fly.
|
||||
products:
|
||||
- cache
|
||||
date: 2025-04-03T18:00:00Z
|
||||
products:
|
||||
- cache
|
||||
date: 2025-04-03
|
||||
---
|
||||
|
||||
|
||||
You can now access all Cloudflare cache purge methods — no matter which plan you’re on. Whether you need to update a single asset or instantly invalidate large portions of your site’s content, you now have the same powerful tools previously reserved for Enterprise customers.
|
||||
|
||||
**Anyone on Cloudflare can now:**
|
||||
|
||||
1. [Purge Everything](/cache/how-to/purge-cache/purge-everything/): Clears all cached content associated with a website.
|
||||
2. [Purge by Prefix](/cache/how-to/purge-cache/purge_by_prefix/): Targets URLs sharing a common prefix.
|
||||
3. [Purge by Hostname](/cache/how-to/purge-cache/purge-by-hostname/): Invalidates content by specific hostnames.
|
||||
4. [Purge by URL (single-file purge)](/cache/how-to/purge-cache/purge-by-single-file/): Precisely targets individual URLs.
|
||||
5. [Purge by Tag](/cache/how-to/purge-cache/purge-by-tags/): Uses Cache-Tag response headers to invalidate grouped assets, offering flexibility for complex cache management scenarios.
|
||||
|
||||
Want to learn how each purge method works, when to use them, or what limits apply to your plan? Dive into our [purge cache documentation](/cache/how-to/purge-cache/) and [API reference](https://developers.cloudflare.com/api/resources/cache/methods/purge/) for all the details.
|
||||
|
||||
Want to learn how each purge method works, when to use them, or what limits apply to your plan? Dive into our [purge cache documentation](/cache/how-to/purge-cache/) and [API reference](https://developers.cloudflare.com/api/resources/cache/methods/purge/) for all the details.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Find security misconfigurations in your AWS cloud environment
|
||||
description: CASB and DLP with Cloud Data Extraction for AWS cloud environments
|
||||
date: 2024-11-22T11:00:00Z
|
||||
date: 2024-11-22
|
||||
---
|
||||
|
||||
import { Render } from "~/components";
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Dark Mode for Zero Trust Dashboard
|
||||
description: Use Dark Mode in the Zero Trust Dashboard
|
||||
date: 2025-04-30T11:00:00Z
|
||||
date: 2025-04-30
|
||||
---
|
||||
|
||||
import { Tabs, TabItem } from "~/components";
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: New Access Analytics in the Cloudflare One Dashboard
|
||||
description: An upgraded analytics experience for Access usage and metrics.
|
||||
date: 2025-05-16T11:00:00Z
|
||||
date: 2025-05-16
|
||||
products:
|
||||
- access
|
||||
---
|
||||
|
|
@ -19,4 +19,4 @@ A new Access Analytics dashboard is now available to all Cloudflare One customer
|
|||
|
||||
|
||||
|
||||
To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Analytics in the side navigation bar.
|
||||
To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Analytics in the side navigation bar.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Cloudflare One Analytics Dashboards and Exportable Access Report
|
||||
description: An upgraded analytics experience for navigating analytics and new report
|
||||
date: 2025-06-05T11:00:00Z
|
||||
date: 2025-06-05
|
||||
products:
|
||||
- access
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: New Gateway Analytics in the Cloudflare One Dashboard
|
||||
description: An upgraded analytics experience for Gateway usage and metrics.
|
||||
date: 2025-05-29T09:00:00Z
|
||||
date: 2025-05-29
|
||||
products:
|
||||
- gateway
|
||||
---
|
||||
|
|
@ -15,6 +15,6 @@ You can now visualize and explore:
|
|||
- Actions Taken: See a clear breakdown of security actions applied by Gateway policies, such as blocks and allows, offering a comprehensive view of your security posture.
|
||||
- Geographic Regions: Gain insight into the global distribution of your traffic.
|
||||
|
||||
|
||||
|
||||
|
||||
To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and go to Analytics in the side navigation bar.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Troubleshoot tunnels with diagnostic logs
|
||||
description: View tunnel diagnostic logs
|
||||
date: 2024-12-19T11:00:00Z
|
||||
date: 2024-12-19
|
||||
---
|
||||
|
||||
import { Render } from "~/components";
|
||||
|
|
|
|||
|
|
@ -3,14 +3,14 @@ title: 40-60% Faster D1 Worker API Requests
|
|||
description: D1's Worker API request latency decreases by 40-60%.
|
||||
products:
|
||||
- d1
|
||||
date: 2025-01-07T18:00:00Z
|
||||
date: 2025-01-07
|
||||
---
|
||||
|
||||
Users making [D1](/d1/) requests via the [Workers API](/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.
|
||||
|
||||
|
||||
|
||||
*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.*
|
||||
_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](/d1/configuration/data-location/#provide-a-location-hint) can be used to influence the geographic location of a database.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: Use D1 Sessions API to leverage read replication.
|
|||
products:
|
||||
- d1
|
||||
- workers
|
||||
date: 2025-04-10T06:00:00Z
|
||||
date: 2025-04-10
|
||||
---
|
||||
|
||||
D1 read replication is available in public beta to help lower average latency and increase overall throughput for read-heavy applications like e-commerce websites or content management tools.
|
||||
|
|
|
|||
|
|
@ -4,10 +4,10 @@ description: D1 REST API request latency improvements.
|
|||
products:
|
||||
- d1
|
||||
- workers
|
||||
date: 2025-05-29T00:00:00Z
|
||||
date: 2025-05-29
|
||||
---
|
||||
|
||||
Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core, centralized data centers, which added network round trips and latency.
|
||||
Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core, centralized data centers, which added network round trips and latency.
|
||||
|
||||
Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outside the United States see a bigger benefit since Cloudflare's primary core data centers reside in the United States.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,13 +1,14 @@
|
|||
---
|
||||
title: Cloudflare One Agent now supports Endpoint Monitoring
|
||||
description: Monitor device health metrics directly from the Cloudflare One agent
|
||||
date: 2025-03-07T6:00:00Z
|
||||
date: 2025-03-07
|
||||
---
|
||||
|
||||
[Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into device, network, and application performance across your Cloudflare SASE deployment. The latest release of the Cloudflare One agent (v2025.1.861) now includes device endpoint monitoring capabilities
|
||||
to provide deeper visibility into end-user device performance which can be analyzed directly from the dashboard.
|
||||
|
||||
Device health metrics are now automatically collected, allowing administrators to:
|
||||
|
||||
- View the last network a user was connected to
|
||||
- Monitor CPU and RAM utilization on devices
|
||||
- Identify resource-intensive processes running on endpoints
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Detect source code leaks with Data Loss Prevention
|
||||
description: Added source code confidence levels to Data Loss Prevention
|
||||
date: 2025-01-20T11:00:00Z
|
||||
date: 2025-01-20
|
||||
---
|
||||
|
||||
import { Render } from "~/components";
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: New predefined detection entry for ICD-11
|
||||
description: ICD-11 is now available for DLP detections.
|
||||
date: 2025-04-14T11:00:00Z
|
||||
date: 2025-04-14
|
||||
---
|
||||
|
||||
You now have access to the World Health Organization (WHO) 2025 edition of the [International Classification of Diseases 11th Revision (ICD-11)](https://www.who.int/news/item/14-02-2025-who-releases-2025-update-to-the-international-classification-of-diseases-%28icd-11%29) as a predefined detection entry. The new dataset can be found in the [Health Information](/cloudflare-one/policies/data-loss-prevention/dlp-profiles/predefined-profiles/#health-information) predefined profile.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,9 @@
|
|||
---
|
||||
title: Send forensic copies to storage without DLP profiles
|
||||
description: HTTP policies can now be configured to send forensic copies for all allow and block policies.
|
||||
date: 2025-05-07T11:00:00Z
|
||||
date: 2025-05-07
|
||||
---
|
||||
|
||||
|
||||
You can now [send DLP forensic copies](/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options/#send-http-requests-to-logpush-destination/) to third-party storage for any HTTP policy with an `Allow` or `Block` action, without needing to include a DLP profile. This change increases flexibility for data handling and forensic investigation use cases.
|
||||
|
||||
By default, Gateway will send all matched HTTP requests to your configured DLP Forensic Copy jobs.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Case Sensitive Custom Word Lists
|
||||
description: Custom Word Lists can now be configured to enforce case sensitivity.
|
||||
date: 2025-05-12T11:00:00Z
|
||||
date: 2025-05-12
|
||||
---
|
||||
|
||||
You can now configure [custom word lists](/cloudflare-one/policies/data-loss-prevention/datasets/#custom-wordlist) to enforce case sensitivity. This setting supports flexibility where needed and aims to reduce false positives where letter casing is critical.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Removed unused meta fields from DNS records
|
||||
description: Cloudflare is removing five fields from the meta object of DNS records.
|
||||
date: 2025-02-02T18:00:00Z
|
||||
date: 2025-02-02
|
||||
---
|
||||
|
||||
Cloudflare is removing five fields from the `meta` object of DNS records. These fields have been unused for more than a year and are no longer set on new records. This change may take up to four weeks to fully roll out.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Improved onboarding for Shopify merchants
|
||||
description: Shopify merchants can easily set up Orange-to-Orange (O2O).
|
||||
date: 2025-06-03T11:00:00Z
|
||||
date: 2025-06-03
|
||||
---
|
||||
|
||||
Shopify merchants can now onboard to **Orange-to-Orange (O2O)** automatically, without needing to contact support or community members.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: NSEC3 support for DNSSEC
|
||||
description: Cloudflare DNSSEC supports NSEC3 for proof of non-existence.
|
||||
date: 2025-06-11T12:00:00Z
|
||||
date: 2025-06-11
|
||||
---
|
||||
|
||||
Enterprise customers can now select NSEC3 as method for proof of non-existence on their zones.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Internal DNS (beta) now manageable in the Cloudflare dashboard
|
||||
description: The Internal DNS (beta) is now fully available in the Cloudflare dashboard.
|
||||
date: 2025-06-16T16:00:00Z
|
||||
date: 2025-06-16
|
||||
---
|
||||
|
||||
Participating beta testers can now fully configure [Internal DNS](/dns/internal-dns/) directly in the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/internal-dns).
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Account-level DNS analytics now available via GraphQL Analytics API
|
||||
description: Authoritative DNS analytics can now be accessed on the account level via the GraphQL Analytics API.
|
||||
date: 2025-06-19T12:00:00Z
|
||||
date: 2025-06-19
|
||||
---
|
||||
|
||||
Authoritative DNS analytics are now available on the **account level** via the [Cloudflare GraphQL Analytics API](/analytics/graphql-api/).
|
||||
|
|
@ -15,9 +15,9 @@ query GetLatestNXDOMAINResponses {
|
|||
viewer {
|
||||
accounts(filter: { accountTag: "a30f822fcd7c401984bf85d8f2a5111c" }) {
|
||||
dnsAnalyticsAdaptive(
|
||||
filter: {
|
||||
date_geq: "2025-06-16",
|
||||
date_leq: "2025-06-18",
|
||||
filter: {
|
||||
date_geq: "2025-06-16"
|
||||
date_leq: "2025-06-18"
|
||||
responseCode: "NXDOMAIN"
|
||||
}
|
||||
limit: 10000
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: Durable Objects now available on Workers Free plan.
|
|||
products:
|
||||
- durable-objects
|
||||
- workers
|
||||
date: 2025-04-07T06:00:00Z
|
||||
date: 2025-04-07
|
||||
---
|
||||
|
||||
Durable Objects can now be used with zero commitment on the [Workers Free plan](/workers/platform/pricing/) allowing you to build AI agents with [Agents SDK](/agents/), collaboration tools, and real-time applications like chat or multiplayer games.
|
||||
|
|
|
|||
|
|
@ -3,11 +3,11 @@ title: SQLite in Durable Objects GA with 10GB storage per object
|
|||
description: SQLite-backed Durable Objects are generally available.
|
||||
products:
|
||||
- durable-objects
|
||||
- workers
|
||||
date: 2025-04-07T06:00:00Z
|
||||
- workers
|
||||
date: 2025-04-07
|
||||
---
|
||||
|
||||
SQLite in Durable Objects is now generally available (GA) with 10GB SQLite database per Durable Object. Since the [public beta](https://blog.cloudflare.com/sqlite-in-durable-objects/) in September 2024, we've added feature parity and robustness for the SQLite storage backend compared to the preexisting key-value (KV) storage backend for Durable Objects.
|
||||
SQLite in Durable Objects is now generally available (GA) with 10GB SQLite database per Durable Object. Since the [public beta](https://blog.cloudflare.com/sqlite-in-durable-objects/) in September 2024, we've added feature parity and robustness for the SQLite storage backend compared to the preexisting key-value (KV) storage backend for Durable Objects.
|
||||
|
||||
SQLite-backed Durable Objects are recommended for all new Durable Object classes, using `new_sqlite_classes` [Wrangler configuration](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class). Only SQLite-backed Durable Objects have access to Storage API's [SQL](/durable-objects/api/storage-api/#sql-api) and [point-in-time recovery](/durable-objects/api/storage-api/#pitr-point-in-time-recovery-api) methods, which provide relational data modeling, SQL querying, and better data management.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: "@cloudflare/actors library with Durable Objects helpers and patter
|
|||
products:
|
||||
- durable-objects
|
||||
- workers
|
||||
date: 2025-06-25T06:00:00Z
|
||||
date: 2025-06-25
|
||||
---
|
||||
|
||||
The new [@cloudflare/actors](https://www.npmjs.com/package/@cloudflare/actors) library is now in beta!
|
||||
|
|
@ -28,7 +28,7 @@ import { Storage } from "@cloudflare/actors/storage";
|
|||
|
||||
export class ChatRoom extends DurableObject<Env> {
|
||||
storage: Storage;
|
||||
|
||||
|
||||
constructor(ctx: DurableObjectState, env: Env) {
|
||||
super(ctx, env)
|
||||
this.storage = new Storage(ctx.storage);
|
||||
|
|
@ -50,7 +50,7 @@ export class ChatRoom extends DurableObject<Env> {
|
|||
}
|
||||
```
|
||||
|
||||
`@cloudflare/actors` library introduces the `Actor` class pattern. `Actor` lets you access Durable Objects without writing the Worker that communicates with your Durable Object (the Worker is created for you). By default, requests are routed to a Durable Object named "default".
|
||||
`@cloudflare/actors` library introduces the `Actor` class pattern. `Actor` lets you access Durable Objects without writing the Worker that communicates with your Durable Object (the Worker is created for you). By default, requests are routed to a Durable Object named "default".
|
||||
|
||||
```js
|
||||
export class MyActor extends Actor<Env> {
|
||||
|
|
|
|||
|
|
@ -1,51 +1,60 @@
|
|||
---
|
||||
title: Threaded replies now possible in Email Workers
|
||||
description: You can now use Email Workers to send multiple replies to the same email thread.
|
||||
date: 2025-03-12T18:00:00Z
|
||||
date: 2025-03-12
|
||||
---
|
||||
|
||||
We’re removing some of the restrictions in Email Routing so that AI Agents and task automation can better handle email workflows, including how Workers can [reply](/email-routing/email-workers/reply-email-workers/) to incoming emails.
|
||||
|
||||
It's now possible to keep a threaded email conversation with an [Email Worker](/email-routing/email-workers/) script as long as:
|
||||
|
||||
* The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
|
||||
* The email can only be replied to once in the same `EmailMessage` event.
|
||||
* The recipient in the reply must match the incoming sender.
|
||||
* The outgoing sender domain must match the same domain that received the email.
|
||||
* Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
|
||||
- The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
|
||||
- The email can only be replied to once in the same `EmailMessage` event.
|
||||
- The recipient in the reply must match the incoming sender.
|
||||
- The outgoing sender domain must match the same domain that received the email.
|
||||
- Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
|
||||
|
||||
Here's an example of a Worker responding to Emails using a Workers AI model:
|
||||
|
||||
```ts title="AI model responding to emails"
|
||||
import PostalMime from "postal-mime";
|
||||
import {createMimeMessage} from "mimetext"
|
||||
import { createMimeMessage } from "mimetext";
|
||||
import { EmailMessage } from "cloudflare:email";
|
||||
|
||||
export default {
|
||||
async email(message, env, ctx) {
|
||||
const email = await PostalMime.parse(message.raw)
|
||||
const res = await env.AI.run('@cf/meta/llama-2-7b-chat-fp16', {
|
||||
messages: [{
|
||||
role: "user",
|
||||
content: email.text ?? ''
|
||||
}]
|
||||
})
|
||||
async email(message, env, ctx) {
|
||||
const email = await PostalMime.parse(message.raw);
|
||||
const res = await env.AI.run("@cf/meta/llama-2-7b-chat-fp16", {
|
||||
messages: [
|
||||
{
|
||||
role: "user",
|
||||
content: email.text ?? "",
|
||||
},
|
||||
],
|
||||
});
|
||||
|
||||
// message-id is generated by mimetext
|
||||
const response = createMimeMessage()
|
||||
response.setHeader("In-Reply-To", message.headers.get("Message-ID")!);
|
||||
response.setSender("agent@example.com");
|
||||
response.setRecipient(message.from);
|
||||
response.setSubject("Llama response");
|
||||
response.addMessage({
|
||||
contentType: 'text/plain',
|
||||
data: res instanceof ReadableStream ? await new Response(res).text() : res.response!
|
||||
})
|
||||
// message-id is generated by mimetext
|
||||
const response = createMimeMessage();
|
||||
response.setHeader("In-Reply-To", message.headers.get("Message-ID")!);
|
||||
response.setSender("agent@example.com");
|
||||
response.setRecipient(message.from);
|
||||
response.setSubject("Llama response");
|
||||
response.addMessage({
|
||||
contentType: "text/plain",
|
||||
data:
|
||||
res instanceof ReadableStream
|
||||
? await new Response(res).text()
|
||||
: res.response!,
|
||||
});
|
||||
|
||||
const replyMessage = new EmailMessage("<email>", message.from, response.asRaw());
|
||||
await message.reply(replyMessage)
|
||||
}
|
||||
const replyMessage = new EmailMessage(
|
||||
"<email>",
|
||||
message.from,
|
||||
response.asRaw(),
|
||||
);
|
||||
await message.reply(replyMessage);
|
||||
},
|
||||
} satisfies ExportedHandler<Env>;
|
||||
```
|
||||
|
||||
See [Reply to emails from Workers](/email-routing/email-workers/reply-email-workers/) for more information.
|
||||
See [Reply to emails from Workers](/email-routing/email-workers/reply-email-workers/) for more information.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Local development support for Email Workers
|
||||
description: Developers can now use wrangler to do local development for Email Workers.
|
||||
date: 2025-04-08T15:00:00Z
|
||||
date: 2025-04-08
|
||||
---
|
||||
|
||||
Email Workers enables developers to programmatically take action on anything that hits their email inbox. If you're building with Email Workers, you can now test the behavior of an Email Worker script, receiving, replying and sending emails in your local environment using `wrangler dev`.
|
||||
|
|
@ -9,7 +9,7 @@ Email Workers enables developers to programmatically take action on anything tha
|
|||
Below is an example that shows you how you can receive messages using the `email()` handler and parse them using [postal-mime](https://www.npmjs.com/package/postal-mime):
|
||||
|
||||
```ts
|
||||
import * as PostalMime from 'postal-mime';
|
||||
import * as PostalMime from "postal-mime";
|
||||
|
||||
export default {
|
||||
async email(message, env, ctx) {
|
||||
|
|
@ -47,31 +47,31 @@ This is what you get in the console:
|
|||
|
||||
```json
|
||||
{
|
||||
headers: [
|
||||
{
|
||||
key: 'received',
|
||||
value: 'from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000'
|
||||
},
|
||||
{ key: 'from', value: '"John" <sender@example.com>' },
|
||||
{ key: 'reply-to', value: 'sender@example.com' },
|
||||
{ key: 'to', value: 'recipient@example.com' },
|
||||
{ key: 'subject', value: 'Testing Email Workers Local Dev' },
|
||||
{ key: 'content-type', value: 'text/html; charset="windows-1252"' },
|
||||
{ key: 'x-mailer', value: 'Curl' },
|
||||
{ key: 'date', value: 'Tue, 27 Aug 2024 08:49:44 -0700' },
|
||||
{
|
||||
key: 'message-id',
|
||||
value: '<6114391943504294873000@ZSH-GHOSTTY>'
|
||||
}
|
||||
],
|
||||
from: { address: 'sender@example.com', name: 'John' },
|
||||
to: [ { address: 'recipient@example.com', name: '' } ],
|
||||
replyTo: [ { address: 'sender@example.com', name: '' } ],
|
||||
subject: 'Testing Email Workers Local Dev',
|
||||
messageId: '<6114391943504294873000@ZSH-GHOSTTY>',
|
||||
date: '2024-08-27T15:49:44.000Z',
|
||||
html: 'Hi there\n',
|
||||
attachments: []
|
||||
"headers": [
|
||||
{
|
||||
"key": "received",
|
||||
"value": "from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000"
|
||||
},
|
||||
{ "key": "from", "value": "\"John\" <sender@example.com>" },
|
||||
{ "key": "reply-to", "value": "sender@example.com" },
|
||||
{ "key": "to", "value": "recipient@example.com" },
|
||||
{ "key": "subject", "value": "Testing Email Workers Local Dev" },
|
||||
{ "key": "content-type", "value": "text/html; charset=\"windows-1252\"" },
|
||||
{ "key": "x-mailer", "value": "Curl" },
|
||||
{ "key": "date", "value": "Tue, 27 Aug 2024 08:49:44 -0700" },
|
||||
{
|
||||
"key": "message-id",
|
||||
"value": "<6114391943504294873000@ZSH-GHOSTTY>"
|
||||
}
|
||||
],
|
||||
"from": { "address": "sender@example.com", "name": "John" },
|
||||
"to": [{ "address": "recipient@example.com", "name": "" }],
|
||||
"replyTo": [{ "address": "sender@example.com", "name": "" }],
|
||||
"subject": "Testing Email Workers Local Dev",
|
||||
"messageId": "<6114391943504294873000@ZSH-GHOSTTY>",
|
||||
"date": "2024-08-27T15:49:44.000Z",
|
||||
"html": "Hi there\n",
|
||||
"attachments": []
|
||||
}
|
||||
```
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Mail authentication requirements for Email Routing
|
||||
description: Emails will need to be authenticated either via SPF or DKIM in order to be forwarded.
|
||||
date: 2025-06-30T10:00:00Z
|
||||
date: 2025-06-30
|
||||
---
|
||||
|
||||
The Email Routing platform supports [SPF](https://datatracker.ietf.org/doc/html/rfc7208) records and [DKIM (DomainKeys Identified Mail)](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signatures and
|
||||
|
|
@ -17,4 +17,4 @@ the forward action may fail due to missing authentication on the incoming email.
|
|||
SPAM has been a long-standing issue with email. By enforcing mail authentication, we will increase the efficiency of identifying abusive senders and blocking
|
||||
bad emails.
|
||||
If you're an email server delivering emails to large mailbox providers, it's likely you already use these protocols; otherwise, please ensure
|
||||
you have them properly configured.
|
||||
you have them properly configured.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Increased transparency for phishing email submissions
|
||||
description: New Email reclassifications tab
|
||||
date: 2024-12-19T11:00:00Z
|
||||
date: 2024-12-19
|
||||
---
|
||||
|
||||
import { Render } from "~/components";
|
||||
|
|
|
|||
|
|
@ -1,14 +1,13 @@
|
|||
---
|
||||
title: Open email attachments with Browser Isolation
|
||||
description: A new attachment section in Email Security allows you to safely open attachments to view and investigate.
|
||||
date: 2025-05-08T19:20:11Z
|
||||
date: 2025-05-08
|
||||
---
|
||||
|
||||
You can now safely open email attachments to view and investigate them.
|
||||
|
||||
What this means is that messages now have a **Attachments** section. Here, you can view processed attachments and their classifications (for example, _Malicious_, _Suspicious_, _Encrypted_). Next to each attachment, a **Browser Isolation** icon allows your team to safely open the file in a **clientless, isolated browser** with no risk to the analyst or your environment.
|
||||
|
||||
|
||||
To use this feature, you must:
|
||||
|
||||
- Enable **Clientless Web Isolation** in your Zero Trust settings.
|
||||
|
|
@ -16,8 +15,7 @@ To use this feature, you must:
|
|||
|
||||
For more details, refer to our [setup guide](/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation/).
|
||||
|
||||
Some attachment types may not render in Browser Isolation. If there is a file type that you would like to be opened with Browser Isolation, reach out to your Cloudflare contact.
|
||||
|
||||
Some attachment types may not render in Browser Isolation. If there is a file type that you would like to be opened with Browser Isolation, reach out to your Cloudflare contact.
|
||||
|
||||
This feature is available across all CES packages:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Open email links with Browser Isolation
|
||||
description: New investigation feature for links
|
||||
date: 2025-05-15T11:00:00Z
|
||||
date: 2025-05-15
|
||||
---
|
||||
|
||||
You can now safely open links in emails to view and investigate them.
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@ title: Dozens of Cloudflare Terraform Provider resources now have proper drift d
|
|||
description: Improper drift detection in the Cloudflare Terraform Provider resulted in dozens of resources always indicating they needed to be updated or replaced.
|
||||
products:
|
||||
- fundamentals
|
||||
date: 2025-03-21T00:00:00Z
|
||||
date: 2025-03-21
|
||||
---
|
||||
|
||||
In [Cloudflare Terraform Provider](https://github.com/cloudflare/terraform-provider-cloudflare) versions 5.2.0 and above, dozens of resources now have proper drift detection. Before this fix, these resources would indicate they needed to be updated or replaced — even if there was no real change. Now, you can rely on your `terraform plan` to only show what resources are expected to change.
|
||||
In [Cloudflare Terraform Provider](https://github.com/cloudflare/terraform-provider-cloudflare) versions 5.2.0 and above, dozens of resources now have proper drift detection. Before this fix, these resources would indicate they needed to be updated or replaced — even if there was no real change. Now, you can rely on your `terraform plan` to only show what resources are expected to change.
|
||||
|
||||
This issue affected [resources](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) related to these products and features:
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Cloudflare Terraform Provider now properly redacts sensitive values
|
|||
description: Resources in the Cloudflare Terraform Provider that have sensitive properties will not show those values in logs.
|
||||
products:
|
||||
- fundamentals
|
||||
date: 2025-03-21T00:00:00Z
|
||||
date: 2025-03-21
|
||||
---
|
||||
|
||||
In the [Cloudflare Terraform Provider](https://github.com/cloudflare/terraform-provider-cloudflare) versions 5.2.0 and above, sensitive properties of resources are redacted in logs. Sensitive properties in [Cloudflare's OpenAPI Schema](https://raw.githubusercontent.com/cloudflare/api-schemas/refs/heads/main/openapi.yaml) are now annotated with `x-sensitive: true`. This results in proper auto-generation of the corresponding Terraform resources, and prevents sensitive values from being shown when you run Terraform commands.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Block files that are password-protected, compressed, or otherwise unscannable.
|
||||
description: Unscannable files for Download and Upload File Types selectors
|
||||
date: 2025-02-03T11:00:00Z
|
||||
date: 2025-02-03
|
||||
products:
|
||||
- dlp
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Secure DNS Locations Management User Role
|
||||
description: Create secure DNS locations using the new Cloudflare Zero Trust Locations Write role.
|
||||
date: 2025-03-21T13:50:40Z
|
||||
date: 2025-03-21
|
||||
products:
|
||||
- gateway
|
||||
hidden: false
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: HTTP redirect and custom block page redirect
|
||||
description: Redirect traffic with a Gateway HTTP Redirect policy, or with the block page in an HTTP or DNS Block policy.
|
||||
date: 2025-04-11T16:30:00Z
|
||||
date: 2025-04-11
|
||||
products:
|
||||
- gateway
|
||||
hidden: false
|
||||
|
|
|
|||
|
|
@ -4,10 +4,11 @@ description: Select your egress IP depending on your upstream fully qualified do
|
|||
products:
|
||||
- gateway
|
||||
hidden: false
|
||||
date: 2025-04-28T11:00:00Z
|
||||
date: 2025-04-28
|
||||
---
|
||||
|
||||
Cloudflare One administrators can now control which egress IP is used based on a destination's fully qualified domain name (FDQN) within Gateway Egress policies.
|
||||
Cloudflare One administrators can now control which egress IP is used based on a destination's fully qualified domain name (FDQN) within Gateway Egress policies.
|
||||
|
||||
- Host, Domain, Content Categories, and Application selectors are now available in the Gateway Egress policy builder in beta.
|
||||
- During the beta period, you can use these selectors with traffic on-ramped to Gateway with the WARP client, proxy endpoints (commonly deployed with PAC files), or Cloudflare Browser Isolation.
|
||||
- For WARP client support, additional configuration is required. For more information, refer to the [WARP client configuration documentation](/cloudflare-one/policies/gateway/egress-policies/#limitations).
|
||||
|
|
|
|||
|
|
@ -1,16 +1,16 @@
|
|||
---
|
||||
title: New Applications Added for DNS Filtering
|
||||
description: Manage outbound traffic for 273 new applications with DNS policy options
|
||||
date: 2025-05-13T11:00:00Z
|
||||
description: Manage outbound traffic for 273 new applications with DNS policy options
|
||||
date: 2025-05-13
|
||||
---
|
||||
|
||||
You can now create DNS policies to manage outbound traffic for an expanded list of applications.
|
||||
|
||||
You can now create DNS policies to manage outbound traffic for an expanded list of applications.
|
||||
This update adds support for 273 new applications, giving you more control over your organization's outbound traffic.
|
||||
|
||||
With this update, you can:
|
||||
+ Create DNS policies for a wider range of applications
|
||||
+ Manage outbound traffic more effectively
|
||||
+ Improve your organization's security and compliance posture
|
||||
|
||||
- Create DNS policies for a wider range of applications
|
||||
- Manage outbound traffic more effectively
|
||||
- Improve your organization's security and compliance posture
|
||||
|
||||
For more information on creating DNS policies, see our [DNS policy documentation](/cloudflare-one/policies/gateway/dns-policies/).
|
||||
|
|
|
|||
|
|
@ -1,26 +1,27 @@
|
|||
---
|
||||
title: Domain Categories improvements
|
||||
description: We have added 7 new Domain Categories and renamed 3 Domain Categories, to better reflect online content and enable DNS filtering
|
||||
date: 2025-05-14T11:00:00Z
|
||||
date: 2025-05-14
|
||||
---
|
||||
|
||||
**New categories added**
|
||||
|
||||
| Parent ID | Parent Name | Category ID | Category Name |
|
||||
| --- | --- | --- | --- |
|
||||
| 1 | Ads | 66 | Advertisements |
|
||||
| 3 | Business & Economy | 185 | Personal Finance |
|
||||
| 3 | Business & Economy | 186 | Brokerage & Investing |
|
||||
| 21 | Security Threats | 187 | Compromised Domain |
|
||||
| 21 | Security Threats | 188 | Potentially Unwanted Software |
|
||||
| 6 | Education | 189 | Reference |
|
||||
| 9 | Government & Politics | 190 | Charity and Non-profit |
|
||||
| Parent ID | Parent Name | Category ID | Category Name |
|
||||
| --------- | --------------------- | ----------- | ----------------------------- |
|
||||
| 1 | Ads | 66 | Advertisements |
|
||||
| 3 | Business & Economy | 185 | Personal Finance |
|
||||
| 3 | Business & Economy | 186 | Brokerage & Investing |
|
||||
| 21 | Security Threats | 187 | Compromised Domain |
|
||||
| 21 | Security Threats | 188 | Potentially Unwanted Software |
|
||||
| 6 | Education | 189 | Reference |
|
||||
| 9 | Government & Politics | 190 | Charity and Non-profit |
|
||||
|
||||
**Changes to existing categories**
|
||||
|
||||
| Original Name | New Name |
|
||||
| --- | --- |
|
||||
| Religion | Religion & Spirituality |
|
||||
| Government | Government/Legal |
|
||||
| Redirect | URL Alias/Redirect |
|
||||
| Original Name | New Name |
|
||||
| ------------- | ----------------------- |
|
||||
| Religion | Religion & Spirituality |
|
||||
| Government | Government/Legal |
|
||||
| Redirect | URL Alias/Redirect |
|
||||
|
||||
Refer to [Gateway domain categories](/cloudflare-one/policies/gateway/domain-categories/) to learn more.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ description: Gateway protocol detection is now available on customer plan types!
|
|||
products:
|
||||
- gateway
|
||||
hidden: false
|
||||
date: 2025-05-27T11:00:00Z
|
||||
date: 2025-05-27
|
||||
---
|
||||
|
||||
All Cloudflare One Gateway users can now use Protocol detection logging and filtering, including those on Pay-as-you-go and Free plans.
|
||||
|
|
|
|||
|
|
@ -4,8 +4,9 @@ description: Gateway Network policies (Layer 4) will be evaluated before HTTP (L
|
|||
products:
|
||||
- gateway
|
||||
hidden: false
|
||||
date: 2025-06-18T11:00:00Z
|
||||
date: 2025-06-18
|
||||
---
|
||||
|
||||
[Gateway](/cloudflare-one/policies/gateway/) will now evaluate [Network (Layer 4) policies](/cloudflare-one/policies/gateway/network-policies/) **before** [HTTP (Layer 7) policies](/cloudflare-one/policies/gateway/http-policies/). This change preserves your existing security posture and does not affect which traffic is filtered — but it may impact how notifications are displayed to end users.
|
||||
|
||||
This change will roll out progressively between **July 14–18, 2025**. If you use HTTP policies, we recommend reviewing your configuration ahead of rollout to ensure the user experience remains consistent.
|
||||
|
|
@ -13,14 +14,16 @@ This change will roll out progressively between **July 14–18, 2025**. If you u
|
|||
### Updated order of enforcement
|
||||
|
||||
**Previous order:**
|
||||
1. DNS policies
|
||||
2. HTTP policies
|
||||
3. Network policies
|
||||
|
||||
1. DNS policies
|
||||
2. HTTP policies
|
||||
3. Network policies
|
||||
|
||||
**New order:**
|
||||
1. DNS policies
|
||||
2. **Network policies**
|
||||
3. **HTTP policies**
|
||||
|
||||
1. DNS policies
|
||||
2. **Network policies**
|
||||
3. **HTTP policies**
|
||||
|
||||
### Action required: Review your Gateway HTTP policies
|
||||
|
||||
|
|
@ -32,6 +35,7 @@ This change may affect block notifications. For example:
|
|||
With the new order, the Network policy will trigger first — and the user will no longer see the HTTP block page.
|
||||
|
||||
To ensure users still receive a block notification, you can:
|
||||
|
||||
- Add a client notification to your Network policy, or
|
||||
- Use only the HTTP policy for that domain.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Up to 10x faster cached queries for Hyperdrive
|
|||
description: Hyperdrive now caches queries in all Cloudflare locations decreasing cache hit latency by up to 90%
|
||||
products:
|
||||
- hyperdrive
|
||||
date: 2024-12-11T18:00:00Z
|
||||
date: 2024-12-11
|
||||
---
|
||||
|
||||
Hyperdrive now caches queries in all Cloudflare locations, decreasing cache hit latency by up to 90%.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Automatic configuration for private databases on Hyperdrive
|
|||
description: Hyperdrive now automatically configures your Cloudflare Tunnel to connect to your private database.
|
||||
products:
|
||||
- hyperdrive
|
||||
date: 2025-01-28T18:00:00Z
|
||||
date: 2025-01-28
|
||||
---
|
||||
|
||||
Hyperdrive now automatically configures your Cloudflare Tunnel to connect to your private database.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Hyperdrive reduces query latency by up to 90% and now supports IP access
|
|||
description: Hyperdrive now pools database connections closer to your database to reduce query latency, and now also provides a documented IP address range for IP ACLs.
|
||||
products:
|
||||
- hyperdrive
|
||||
date: 2025-03-07T18:00:00Z
|
||||
date: 2025-03-07
|
||||
---
|
||||
|
||||
Hyperdrive now pools database connections in one or more regions close to your database. This means that your uncached queries and new database connections have up to 90% less latency as measured from connection pools.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Hyperdrive Free plan makes fast, global database access available to all
|
|||
description: Hyperdrive is now available on the Free plan of Cloudflare Workers, enabling you to build Workers that connect to PostgreSQL or MySQL databases without compromise.
|
||||
products:
|
||||
- hyperdrive
|
||||
date: 2025-04-08T18:00:00Z
|
||||
date: 2025-04-08
|
||||
---
|
||||
|
||||
Hyperdrive is now available on the Free plan of Cloudflare Workers, enabling you to build Workers that connect to PostgreSQL or MySQL databases without compromise.
|
||||
|
|
@ -15,4 +15,4 @@ If you want to learn more about how Hyperdrive works, read the [deep dive](https
|
|||
|
||||
|
||||
|
||||
Visit the docs to [get started](/hyperdrive/get-started/) with Hyperdrive for PostgreSQL or MySQL.
|
||||
Visit the docs to [get started](/hyperdrive/get-started/) with Hyperdrive for PostgreSQL or MySQL.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Hyperdrive introduces support for MySQL and MySQL-compatible databases
|
|||
description: You can now connect to MySQL databases from your Workers using Hyperdrive for optimal performance
|
||||
products:
|
||||
- hyperdrive
|
||||
date: 2025-04-08T14:00:00Z
|
||||
date: 2025-04-08
|
||||
---
|
||||
|
||||
import { Code } from "~/components";
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Hyperdrive now supports custom TLS/SSL certificates
|
|||
description: You can now configure custom certificates for secure database connections with Hyperdrive, including both server certificate verification and client certificates
|
||||
products:
|
||||
- hyperdrive
|
||||
date: 2025-04-09T17:00:00Z
|
||||
date: 2025-04-09
|
||||
---
|
||||
|
||||
import { Code } from "~/components";
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Hyperdrive achieves FedRAMP Moderate-Impact Authorization
|
|||
description: Hyperdrive has been approved for FedRAMP Authorization and is now available in the FedRAMP Marketplace
|
||||
products:
|
||||
- hyperdrive
|
||||
date: 2025-05-14T17:00:00Z
|
||||
date: 2025-05-14
|
||||
---
|
||||
|
||||
import { Code } from "~/components";
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Hyperdrive now supports configuring the amount of database connections
|
|||
description: Hyperdrive configurations can now be set to use a specific number of connections to your origin database.
|
||||
products:
|
||||
- hyperdrive
|
||||
date: 2025-07-03T18:00:00Z
|
||||
date: 2025-07-03
|
||||
---
|
||||
|
||||
You can now specify the number of connections your Hyperdrive configuration uses to connect to your origin database.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: "Bind the Images API to your Worker"
|
||||
description: >
|
||||
You can now interact with the Images API directly in your Worker with Image Bindings.
|
||||
date: 2025-02-24T12:00:00Z
|
||||
date: 2025-02-24
|
||||
---
|
||||
|
||||
import { WranglerConfig } from "~/components";
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Workers KV namespace limits increased to 1000
|
|||
description: You can now have up to 1000 Workers KV namespaces per account.
|
||||
products:
|
||||
- kv
|
||||
date: 2025-01-28T14:00:00Z
|
||||
date: 2025-01-28
|
||||
---
|
||||
|
||||
You can now have up to 1000 Workers KV namespaces per account.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Read multiple keys from Workers KV with bulk reads
|
|||
description: You can now retrieve up to 100 keys in a single bulk read request to Workers KV.
|
||||
products:
|
||||
- kv
|
||||
date: 2025-04-17T14:00:00Z
|
||||
date: 2025-04-17
|
||||
---
|
||||
|
||||
You can now retrieve up to 100 keys in a single bulk read request made to Workers KV using the binding.
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
---
|
||||
title: Log Explorer is GA
|
||||
description: Log Explorer is now GA - providing native observability and forensics
|
||||
date: 2025-06-18T11:00:00Z
|
||||
date: 2025-06-18
|
||||
---
|
||||
|
||||
[Log Explorer](/log-explorer/) is now GA, providing native observability and forensics for traffic flowing through Cloudflare.
|
||||
|
||||
[Log Explorer](/log-explorer/) is now GA, providing native observability and forensics for traffic flowing through Cloudflare.
|
||||
|
||||
Search and analyze your logs, natively in the Cloudflare dashboard. These logs are also stored in Cloudflare's network, eliminating many of the costs associated with other log providers.
|
||||
|
||||
|
|
@ -14,7 +14,7 @@ With Log Explorer, you can now:
|
|||
|
||||
- **Monitor security and performance issues with custom dashboards** – use natural language to define charts for measuring response time, error rates, top statistics and more.
|
||||
- **Investigate and troubleshoot issues with Log Search** – use data type-aware search filters or custom sql to investigate detailed logs.
|
||||
- **Save time and collaborate with saved queries** – save Log Search queries for repeated use or sharing with other users in your account.
|
||||
- **Save time and collaborate with saved queries** – save Log Search queries for repeated use or sharing with other users in your account.
|
||||
- **Access Log Explorer at the account and zone level** – easily find Log Explorer at the account and zone level for querying any dataset.
|
||||
|
||||
For help getting started, refer to [our documentation](/log-explorer/).
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
title: One-click Logpush Setup with R2 Object Storage
|
||||
description: Seamlessly configure Logpush to R2 in just one click.
|
||||
date: 2025-03-06T11:00:00Z
|
||||
date: 2025-03-06
|
||||
---
|
||||
|
||||
We’ve streamlined the [Logpush](/logs/get-started/) setup process by integrating R2 bucket creation directly into the Logpush workflow!
|
||||
We’ve streamlined the [Logpush](/logs/get-started/) setup process by integrating R2 bucket creation directly into the Logpush workflow!
|
||||
|
||||
Now, you no longer need to navigate multiple pages to manually create an R2 bucket or copy credentials. With this update, you can seamlessly **configure a Logpush job to R2 in just one click**, reducing friction and making setup faster and easier.
|
||||
|
||||
This enhancement makes it easier for customers to adopt Logpush and R2.
|
||||
This enhancement makes it easier for customers to adopt Logpush and R2.
|
||||
|
||||
For more details refer to our [Logs](/logs/get-started/enable-destinations/r2/) documentation.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Custom fields raw and transformed values support
|
||||
description: Configure request header and response headers values can log eiterh raw or transformed value
|
||||
date: 2025-04-18T11:00:00Z
|
||||
date: 2025-04-18
|
||||
---
|
||||
|
||||
Custom Fields now support logging both **raw and transformed values** for request and response headers in the HTTP requests dataset.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Generate customized terraform files for building cloud network on-ramps
|
||||
description: Download cloud onramp terraform
|
||||
date: 2024-12-05T11:00:00Z
|
||||
date: 2024-12-05
|
||||
---
|
||||
|
||||
import { Render } from "~/components";
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Search for custom rules using rule name and/or ID
|
||||
description: New UI improvements for Magic Firewall
|
||||
date: 2024-10-02T11:00:00Z
|
||||
date: 2024-10-02
|
||||
---
|
||||
|
||||
The Magic Firewall dashboard now allows you to search custom rules using the rule name and/or ID.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Try out Magic Network Monitoring
|
||||
description: The free version of Magic Network Monitoring is available to all customers
|
||||
date: 2024-09-24T11:00:00Z
|
||||
date: 2024-09-24
|
||||
---
|
||||
|
||||
The free version of Magic Network Monitoring (MNM) is now available to everyone with a Cloudflare account by default.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Configure your Magic WAN Connector to connect via static IP assigment
|
||||
description: Local console access for bootstrapping Magic WAN Connector
|
||||
date: 2025-02-14T11:00:00Z
|
||||
date: 2025-02-14
|
||||
---
|
||||
|
||||
You can now locally configure your [Magic WAN Connector](/magic-wan/configuration/connector/) to work in a static IP configuration.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
title: Establish BGP peering over Direct CNI circuits
|
||||
description: BGP support for Cloudflare Network Interconnect (CNI)
|
||||
date: 2024-12-17T11:00:00Z
|
||||
date: 2024-12-17
|
||||
products:
|
||||
- magic-transit
|
||||
- magic-wan
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ products:
|
|||
- pipelines
|
||||
- r2
|
||||
- workers
|
||||
date: 2025-04-10T12:00:00Z
|
||||
date: 2025-04-10
|
||||
---
|
||||
|
||||
[Cloudflare Pipelines](/pipelines) is now available in beta, to all users with a [Workers Paid](/workers/platform/pricing) plan.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Super Slurper now transfers data to R2 up to 5x faster
|
|||
description: Super Slurper now transfers data from cloud object storage providers like AWS S3 and Google Cloud Storage to Cloudflare R2 up to 5x faster
|
||||
products:
|
||||
- r2
|
||||
date: 2025-02-14T19:00:00Z
|
||||
date: 2025-02-14
|
||||
---
|
||||
|
||||
[Super Slurper](/r2/data-migration/super-slurper/) now transfers data from cloud object storage providers like AWS S3 and Google Cloud Storage to [Cloudflare R2](/r2/) up to 5x faster than it did before.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Super Slurper now supports migrations from all S3-compatible storage prov
|
|||
description: Super Slurper now supports migrations from all S3-compatible storage providers
|
||||
products:
|
||||
- r2
|
||||
date: 2025-02-24T19:00:00Z
|
||||
date: 2025-02-24
|
||||
---
|
||||
|
||||
[Super Slurper](/r2/data-migration/super-slurper/) can now migrate data from any S3-compatible object storage provider to [Cloudflare R2](/r2/). This includes transfers from services like MinIO, Wasabi, Backblaze B2, and DigitalOcean Spaces.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: Set retention polices for your R2 bucket with bucket locks
|
|||
description: Set retention polices for your R2 bucket with bucket locks
|
||||
products:
|
||||
- r2
|
||||
date: 2025-03-06T10:00:00Z
|
||||
date: 2025-03-06
|
||||
---
|
||||
|
||||
You can now use [bucket locks](/r2/buckets/bucket-locks/) to set retention policies on your [R2 buckets](/r2/buckets/) (or specific prefixes within your buckets) for a specified period — or indefinitely. This can help ensure compliance by protecting important data from accidental or malicious deletion.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ title: R2 Data Catalog is a managed Apache Iceberg data catalog built directly i
|
|||
description: A managed Apache Iceberg data catalog built directly into R2 buckets
|
||||
products:
|
||||
- r2
|
||||
date: 2025-04-10T13:00:00Z
|
||||
date: 2025-04-10
|
||||
---
|
||||
|
||||
Today, we're launching [R2 Data Catalog](/r2/data-catalog/) in open beta, a managed Apache Iceberg catalog built directly into your [Cloudflare R2](/r2/) bucket.
|
||||
|
|
|
|||
|
|
@ -3,14 +3,13 @@ title: R2 Dashboard experience gets new updates
|
|||
description: R2 Dashboard experience gets new updates
|
||||
products:
|
||||
- r2
|
||||
date: 2025-05-01T13:00:00Z
|
||||
date: 2025-05-01
|
||||
---
|
||||
|
||||
We're excited to announce several improvements to the [Cloudflare R2](/r2/) dashboard experience that make managing your object storage easier and more intuitive:
|
||||
|
||||
|
||||
|
||||
|
||||
#### All-new settings page
|
||||
|
||||
We've redesigned the bucket settings page, giving you a centralized location to manage all your bucket configurations in one place.
|
||||
|
|
@ -25,4 +24,4 @@ We've redesigned the bucket settings page, giving you a centralized location to
|
|||
- Renamed "r2.dev domain" to "Public Development URL" for better clarity when exposing bucket contents for non-production workloads.
|
||||
- Public Access status now clearly displays "Enabled" when your bucket is exposed to the internet (via Public Development URL or Custom Domains).
|
||||
|
||||
We've also made numerous other usability improvements across the board to make your R2 experience smoother and more productive.
|
||||
We've also made numerous other usability improvements across the board to make your R2 experience smoother and more productive.
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Reference in a new issue