Changelog · Rules

Wildcard support added to Ruleset Engine products

Wed, 31 Jul 2024 08:00:00 EST

Wildcards are now supported across our Ruleset Engine-based products, including Single Redirects, Cache Rules, Transform Rules, WAF, Waiting Room, and more:

You can now use the wildcard and strict wildcard operators with any string field in the Ruleset Engine, such as full URI, host, headers, cookies, user-agent, and country. For more details, refer to Operators and Wildcard matching.
In Single Redirects, the wildcard_replace() function allows you to use segments matched by the wildcard and strict wildcard operators in redirect URL targets. For more information, refer to Functions.

Cloudflare Snippets now available to all paid customers

Mon, 01 Jul 2024 08:00:00 EST

Cloudflare Snippets (alpha) are now available to all paid customers.

Cloudflare Snippets now available to all Enterprise customers

Mon, 03 Jun 2024 08:00:00 EST

Cloudflare Snippets (alpha) are now available to all Enterprise customers. Customers in other paid plans will gradually get access throughout 2024.

Page Rules migration

Tue, 14 May 2024 08:00:00 EST

The Page Rules migration guide is now available for users interested in transitioning to modern Rules features instead of Page Rules. Explore the guide for detailed instructions on migrating your configurations.

New Configuration Rules setting for Web Analytics (RUM)

Mon, 13 May 2024 08:00:00 EST

You can now turn off Cloudflare Web Analytics, also known as Real User Monitoring (RUM), for specific requests using a configuration rule.

New Configuration Rules setting for Cloudflare Fonts

Mon, 29 Apr 2024 08:00:00 EST

You can now turn on or off Cloudflare Fonts for specific requests using a configuration rule.

New TLS fields in rule expressions

Fri, 22 Mar 2024 08:00:00 EST

Customers can now use new fields cf.tls_client_hello_length (the length of the client hello message sent in a TLS handshake), cf.tls_client_random (the value of the 32-byte random value provided by the client in a TLS handshake), and cf.tls_client_extensions_sha1 (the SHA-1 fingerprint of TLS client extensions) in various products built on Ruleset Engine.

Origin Rules now allow port numbers in Host Header Override

Wed, 20 Mar 2024 08:00:00 EST

Customers can now use arbitrary port numbers in Host Header Override in Origin Rules. Previously, only hostname was allowed as a value (for example, example.com). Now, you can set the value to hostname:port (for example, example.com:1234) as well.