Set rate limits and exemptions
Restricting consumption of resources and rate of requests
Different types of rate limits are defined in different parts of the Reblaze interface.
Static rate limits for entire sites/applications: A static rate limiting capability is available via the Application IP Rate Limits settings within Proxy Templates. This is simple, IP-based rate limiting that applies globally to every site/application based upon that Proxy Template.
Granular rate limiting: More powerful capabilities are available through Rate Limit Rules, including variable scope, multiple criteria for tracking requestors, actions, and more. These Rules are then associated with specific locations/URLs through Security Policies.
Global enforcement by traffic source: Requestors who submit excessive requests across the planet can be banned for configured lengths of time. This can be done via Dynamic Rules.
Creating Rate Limiting Exemptions
To exempt one or more traffic sources from all filtering, follow the instructions here: Bypass Reblaze for Loadtesting or Other Purposes.
To exempt a traffic source from rate limiting only, do the following:
Determine a unique tag that will identify the traffic source(s).
There might already be one in use by the system. For example, to exempt an entire ASN, the automatic tag for that ASN can be used.
If not, then create a Global Filter that will assign a unique tag to requests from the traffic source(s) in question.
Add the tag to the Exclude filter list in the applicable Rate Limit Rules and Dynamic Rules.
Last updated