Override expressions
Set an override expression for the HTTP DDoS Attack Protection managed ruleset to define a specific scope for sensitivity level or action adjustments.
For example, you can set different sensitivity levels for different request URI paths: a medium sensitivity level for URI path A
and a low sensitivity level for URI path B
.
You can use the following fields in override expressions:
cf.bot_management.ja3_hash
cf.bot_management.ja4
cf.client.bot
cf.threat_score
cf.tls_cipher
cf.tls_client_auth.cert_verified
cf.tls_version
cf.verified_bot_category
http.cookie
http.host
http.referer
http.request.headers
http.request.headers.names
http.request.headers.truncated
http.request.headers.values
http.request.uri
http.request.uri.path
http.request.uri.path.extension
http.request.uri.query
http.request.full_uri
http.request.method
http.request.version
http.request.cookies
http.user_agent
http.x_forwarded_for
ip.geoip.asnum
ip.geoip.continent
ip.geoip.country
ip.geoip.is_in_european_union
ip.src
ip.src.asnum
ip.src.continent
ip.src.country
ip.src.is_in_european_union
ssl
Refer to the Fields reference in the Rules language documentation for more information.
An expression is not an allowlist and does not become part of the attack fingerprint. The expression applies to the scope of the override and is used right before applying a mitigation action which determines if the sensitivity level and action need to be adjusted.
For example, if you have an expression matching packets with a specific source IP address and the override sets the sensitivity level to low, this override will only lower the sensitivity level for traffic that comes directly from that source IP address. If the DDoS protection system detects an attack coming from many source IP addresses targeted at a single destination IP and port, the generated fingerprint will only match the common criteria of the attack which, in this example, does not include the source IP address. The system will trigger the required mitigation actions at the default high sensitivity level because the traffic did not come from the user-provided source IP address. Therefore, traffic from the source IP in the override expression may still be blocked because the fingerprint only contains the destination IP address and port of the attack.
Was this helpful?
- Resources
- API
- New to Cloudflare?
- Products
- Sponsorships
- Open Source
- Support
- Help Center
- System Status
- Compliance
- GDPR
- Company
- cloudflare.com
- Our team
- Careers
- 2025 Cloudflare, Inc.
- Privacy Policy
- Terms of Use
- Report Security Issues
- Trademark