CCloud Releases
Home
Following

Cloud Releases

Service catalogues and updates come from each provider's public product listing and announcements.

Explore

  • Home
  • Latest updates
  • Following

About

  • About
  • Contact
  • Privacy Policy
  • Terms of Use

Providers

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
  • Cloudflare

Not affiliated with any cloud provider. Product names and logos belong to their owners.

  1. Providers
  2. ›Cloudflare
  3. ›Rules
  4. ›Update

Feature•Jul 16, 2026

Bot management fields and ASN support in Cache Rules

RulesCloudflare · Core platform

Cache Rules now supports bot management fields and the ip.src.asnum field in expression filters. You can now build cache policies that differentiate between automated and human traffic, or segment caching behavior by autonomous system number (ASN).

This allows you to apply different caching strategies for verified bots, high-risk traffic, or specific network operators without affecting legitimate user requests. For example, you can set shorter cache TTLs for suspected bot traffic or bypass cache entirely for requests from specific ASNs.

New fields

The following fields are now available in Cache Rules expressions:

Field · Type · Description

cf.bot_management.score · Number · Bot score from 1 to 99, where a lower value indicates a higher likelihood that the request originates from a bot.

cf.bot_management.ja3_hash · String · JA3 fingerprint of the request, which helps identify the client making the connection.

cf.bot_management.ja4 · String · JA4 fingerprint of the request, which provides a more detailed client identification than JA3.

cf.bot_management.verified_bot · Boolean · Whether the request originates from a verified bot, such as a search engine crawler.

cf.bot_management.static_resource · Boolean · Whether the request is for a static resource and therefore exempt from bot detection.

cf.bot_management.js_detection.passed · Boolean · Whether the browser passed JavaScript detection when the feature is enabled.

cf.bot_management.detection_ids · Array<Number> · List of IDs that correspond to Bot Management heuristic detections made on the request.

cf.bot_management.tags · Array<String> · List of tags associated with the bot traffic, such as API, GOOGLE, or BING. Match a tag with an expression such as any(cf.bot_management.tags[*] eq "API").

cf.bot_management.signed_agent · Boolean · Whether the request originates from a known agent that identifies itself with Web Bot Auth.

cf.bot_management.corporate_proxy · Boolean · Whether the request originates from a known corporate proxy.

ip.src.asnum · Number · The autonomous system number (ASN) of the incoming request's IP address.

Note

Bot management fields require a Bot Management subscription. ip.src.asnum is available on all plans.

Example

Cache Rules expressions support combining these fields with other criteria. The following example sets a shorter cache TTL for API requests that originate from a high-risk bot or an unexpected ASN:

(http.request.uri.path contains "/api/" and cf.bot_management.score lt 30) or (http.request.uri.path contains "/api/" and not ip.src.asnum in {12345 67890})

To learn more, refer to the Cache Rules documentation and the Fields reference.

Read the original announcement↗

More from Rules

All Rules updates →
  1. Failed detections field available in Rules

    You can now use cf.appsec.request.failed_detections to control how your rules handle requests when a security detection reports a failure.

    Rules•Feature•Oct 9, 2026
  2. hash_in_range() is globally available for HTTP products

    hash_in_range() is globally available for HTTP products on all plans. It hashes fields into an integer within a specified range. Use this result to select a portion of requests.

    Rules•Feature•Oct 2, 2026
  3. Handle missing values with coalesce()

    The coalesce() function returns the first argument that is not nil. Use it to provide a fallback in rule expressions:

    Rules•Feature•Oct 1, 2026
  4. Compare dynamic values in Rules expressions

    Cloudflare Rules expressions now support dynamic values on both sides of equality and ordering comparisons. You can compare request fields or function results with one another.

    Rules•Feature•Oct 1, 2026
  5. concat() now supports up to 32 arguments

    The concat() function in Cloudflare Rules now accepts up to 32 arguments, increased from 16. This allows you to build richer dynamic values directly in Rules expressions and simplify configurations that combine request data.

    Rules•Feature•Sep 22, 2026