For the complete documentation index, see llms.txt. This page is also available as Markdown.

User Agent ACL

Control access to content by allowing or blocking requests based on User-Agent header values.

User Agent ACL allows you to control access to content by evaluating the User-Agent header of incoming requests.

You can create whitelist or blacklist rules using full or partial User-Agent values to allow or deny access for specific browsers, applications, crawlers, or automated clients.

Configure User Agent ACL

Enable the Feature

Turn Status to On.

Select the Rule Mode

Choose one of the following modes:

  • Whitelist — Only matching User-Agent values are allowed.

  • Blacklist — Matching User-Agent values are blocked.

Select the Match Type

Choose how User-Agent values should be evaluated:

  • Contains — Matches any User-Agent containing the specified value.

  • Exact Match — Requires the entire User-Agent value to match exactly.

Add User-Agent Rules

Enter the User-Agent value and click + to add the rule.

Save the Configuration

Click Submit to apply the changes.

How It Works

The CDN evaluates the User-Agent request header against the configured rules.

Depending on the selected mode:

  • Matching requests may be allowed.

  • Matching requests may be blocked.

Requests that do not match the configured rules follow the behavior defined by the selected whitelist or blacklist mode.

Common Use Cases

  • Block known crawlers or scraping tools

  • Restrict access to specific client applications

  • Allow access only to approved applications

  • Filter unwanted automated traffic

Important Notes

  • User-Agent values are supplied by the client and can be modified or spoofed.

  • User Agent ACL should not be used as the sole security mechanism for protecting sensitive content.

  • Consider combining User Agent ACL with Rate Limiting, WAF, Security Token, or IP Restriction for stronger protection.

Last updated

Was this helpful?