All months

Changelog · 2024-04

April 2024

Content filters, new rule actions for static content and edge functions, US-East and Japan shielding regions, and IPv6 support in IP rules.

10 updates across 7 products shipped this month.

New 3

Back to top
New CDN

US-East and Japan shielding regions

Two new shielding regions are available — US-East (Atlanta) and Japan (Tokyo) — bringing the total to five options. Shield region can be selected from the dashboard under project settings.

New Edge functions

Content filters

You can now use content filters to change response content before it reaches visitors, for example to rewrite page markup as it is served. Create and edit filters in the dashboard code editor, where new filters start with example code that you can adapt, and run them with the new Execute content filter rule action.

Related documentation: Content filters

New Rules

Static content, edge function and content filter actions

Page rules have three new actions. The Serve existing static content action returns content that you already published at another path, such as /about-us, for matching requests. The Execute serverless function action runs one of your edge functions. The Execute content filter action applies one of your content filters to the response that is served. That response can be one of your static pages, the output of an edge function or an HTML response from a rule that runs later. You can combine these actions with the existing rule conditions: domain, URL, country, HTTP method, IP address and cookie.

Related documentation: Page Rules: Actions

Improved 6

Back to top
Improved API

v1 routes maintained alongside v2

As the v2 API rolls out, v1 routes remain available and continue to be maintained, so existing integrations keep working without changes.

Improved Rules

IPv6 in IP rules

IP match rules now accept IPv6 addresses alongside IPv4 addresses, as individual addresses or CIDR ranges, and the edge matches them against the IPv6 addresses of visitors.

Improved Rules

Query strings passed to redirect and proxy destinations

Redirect and proxy rules now keep the request's query string. For example, with a redirect rule from /old-page to /new-page, a request for /old-page?ref=footer goes to /new-page?ref=footer. To match on a specific query string, include it in the URL pattern, for example /search?q=*. The original query string is then not added to the destination again.

Improved Rules

Full path capture in proxy and redirect destinations

Proxy and redirect rules now accept $* in the destination, which is replaced with the full matched request path. This is useful when one rule matches several URL patterns, such as /blogs/* and /posts/*, and you want each request to keep its own path at the destination. The existing $1 to $5 patterns still insert individual wildcard matches.

Improved SDKs

Go admin client rules update

In the Go admin client, rules now take a list of URLs, matching the multi-URL rules added in March. It also supports recent API changes.

Improved WAF

Hit rate limiting in log filters

The type filter on WAF logs now includes WAF hit rate limiting, so you can narrow the WAF log view to only the requests that were rate-limited for repeatedly triggering WAF rules.

Fixed 1

Back to top
Fixed Dashboard

WYSIWYG page editor

Saving content via the WYSIWYG editor was failing in some cases. This has been resolved.