This article explains the legacy version of
The use of multiple rules provides greater control when determining how requests will be rate limited.
Common use cases for multiple rules:
- Define site-specific rules.
- Define rules based on traffic profiles.
- Define rules that track abnormal traffic patterns.
Rule Order
The order in which rules are listed is critical, since it determines which rule will be applied to a request.
It is recommended to order rules according to how they identify requests. Stricter rules that identify requests using multiple conditions should be placed closer to the top of the list, while catch-all rules should be placed closer to the bottom. This ensures that rules are applied to requests as intended.
Key information:
- Rules are processed in the order in which they are listed (i.e., top to bottom).
-
Only a single rule may be applied to a request.
- This is determined according to the first rule that the request satisfies. A request satisfies a rule when it meets all match conditions associated with that rule.
- Once a request satisfies a rule, all subsequent rules will be skipped.
- Reorder rules by dragging the
icon that appears directly to the right of the rule name.
More Information