You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Category Filtering in the Network Policy Builder
10
+
description: |-
11
+
Gateway users can now create Network Policies with Content Categories and Security Risks traffic selectors. This update simplifies malicious traffic blocking and streamlines network monitoring for improved security management.
title: "Fixed create instance API in Workers bindings"
10
+
description: |-
11
+
You can now call `create()` without any arguments when using the [Workers API](/workflows/build/workers-api/#create) for Workflows. Workflows will automatically generate the ID of the Workflow on your behalf.
12
+
13
+
This addresses a bug that caused calls to `create()` to fail when provided with no arguments.
14
+
- publish_date: "2024-11-20"
15
+
title: "Multiple Workflows in local development now supported"
16
+
description: |-
17
+
Local development with `wrangler dev` now correctly supports multiple Workflow definitions per script.
18
+
19
+
There is no change to production Workflows, where multiple Workflow definitions per Worker script was already supported.
Copy file name to clipboardExpand all lines: src/content/docs/ai-gateway/configuration/caching.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,9 @@ Enable and customize your gateway cache to serve requests directly from Cloudfla
13
13
14
14
:::note
15
15
16
-
Currently caching is supported only for text and image responses, and it applies only to identical requests. This is helpful for use cases when there are limited prompt options - for example, a support bot that asks "How can I help you?" and lets the user select an answer from a limited set of options works well with the current caching configuration.
16
+
Currently caching is supported only for text and image responses, and it applies only to identical requests.
17
+
18
+
This is helpful for use cases when there are limited prompt options - for example, a support bot that asks "How can I help you?" and lets the user select an answer from a limited set of options works well with the current caching configuration.
17
19
We plan on adding semantic search for caching in the future to improve cache hit rates.
Copy file name to clipboardExpand all lines: src/content/docs/ddos-protection/botnet-threat-feed.mdx
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,8 @@ A single DDoS attack consisting of thousands of bots can involve as little as on
23
23
24
24
In the case of HTTPS DDoS attacks, service providers only see encrypted payloads leaving their network without any possibility to decrypt or understand if it is malicious or legitimate traffic. However, Cloudflare can see an entire attack and all of its sources if the attack targets an Internet property that uses Cloudflare's services. This global view can help service providers stop the abusers.
25
25
26
+
For more details, refer to [How DDoS protection works](/ddos-protection/about/how-ddos-protection-works/).
27
+
26
28
## Availability
27
29
28
30
The Cloudflare DDoS Botnet Threat Feed is available for free to service providers. For more information, refer to the [Terms of Use](https://www.cloudflare.com/en-gb/service-specific-terms-application-services/#ddos-botnet-threat-feed).
@@ -45,6 +47,10 @@ Make sure that:
45
47
4. On the list of ASNs configured for your threat feed, select **Add ASN**.
46
48
5. You will be redirected to the PeeringDB authentication page, where you can log in and consent to share the affiliation data with us. You will be redirected back to the configuration page once it is successful.
47
49
50
+
:::note
51
+
You can add multiple ASNs to your threat feed.
52
+
:::
53
+
48
54
### 2. Obtain Cloudflare API token
49
55
50
56
You must [obtain a Cloudflare API token](/fundamentals/api/get-started/create-token/) with at least the following account-level permission:
@@ -66,6 +72,7 @@ Invoke one of the Botnet Threat Feed API endpoints:
66
72
67
73
- The API URI path is planned to change from `.../botnet_feed/...` to `.../ddos_botnet_feed/...` in the future.
68
74
- Responses with no IP addresses in the results (empty state) will return an `HTTP 200` status code (success), with an empty list in the `result` property.
75
+
- When the response is a success but the result is `0` or `null`, this means that there are no detected offenses.
69
76
:::
70
77
71
78
To invoke an API endpoint, append the operation endpoint to the Cloudflare API base URL:
Copy file name to clipboardExpand all lines: src/content/docs/workers/configuration/smart-placement.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,8 @@ Smart Placement only considers candidate locations where the Worker has previous
31
31
32
32
Smart Placement only affects the execution of [fetch event handlers](/workers/runtime-apis/handlers/fetch/). Workers without a fetch event handler will be ignored by Smart Placement. For Workers with both fetch and non-fetch event handlers, Smart Placement will only affect the execution of the fetch event handler.
33
33
34
+
Similarly, Smart Placement will not affect where [static assets](/workers/static-assets/) are served from. Static assets will continue to be served from the location nearest to the incoming request. If a Worker is invoked and your code retrieves assets via the [static assets binding](https://developers.cloudflare.com/workers/static-assets/binding/), then assets will be served from the location that your Worker runs in.
35
+
34
36
## Enable Smart Placement
35
37
36
38
Smart Placement is available to users on all Workers plans.
[^1]: Does not currently support Workers with static assets. For more details on which bindings are supported in remote development, [refer to the docs](/workers/testing/local-development/#supported-resource-bindings-in-different-environments).
85
85
@@ -89,10 +89,8 @@ We plan to bridge the gaps between Workers and Pages and provide ways to migrate
89
89
90
90
[^4]: You can handle redirects by adding code to your Worker (a [community package](https://npmjs.com/package/redirects-in-workers) is available for `_redirects` support), or you can use [Bulk Redirects](/rules/url-forwarding/bulk-redirects/).
91
91
92
-
[^5]: You cannot yet enable [Smart Placement](/workers/configuration/smart-placement/) for Workers with static assets. This is a temporary limitation we are working to remove.
92
+
[^5]: To [use Durable Objects with your Cloudflare Pages project](/pages/functions/bindings/#durable-objects), you must create a separate Worker with a Durable Object and then declare a binding to it in both your Production and Preview environments. Using Durable Objects with Workers is simpler and recommended.
93
93
94
-
[^6]: To [use Durable Objects with your Cloudflare Pages project](/pages/functions/bindings/#durable-objects), you must create a separate Worker with a Durable Object and then declare a binding to it in both your Production and Preview environments. Using Durable Objects with Workers is simpler and recommended.
94
+
[^6]: Workers [supports popular frameworks](/workers/frameworks/), many of which implement file-based routing.
95
95
96
-
[^7]: Workers [supports popular frameworks](/workers/frameworks/), many of which implement file-based routing.
97
-
98
-
[^8]: Everything that is possible with Pages Functions can also be achieved by adding code to your Worker or by using framework-specific plugins for relevant third party tools.
96
+
[^7]: Everything that is possible with Pages Functions can also be achieved by adding code to your Worker or by using framework-specific plugins for relevant third party tools.
0 commit comments