Advanced Rate Limiter

ARL (Advanced Rate Limiter) is a module for controlling and limiting the load on web apps. The module allows you to set a limit on the number of HTTP requests over a certain period of time. All requests above the limit will be blocked. You can set a single limit for all traffic or configure different limits to segment requests by certain parameters. For the purposes of limits, you can count requests one by one or group them together based on specified characteristics.

ARL pros and features:

• Backend protection against sharp load increases and backend health preservation.
• Additional API protection by controlling HTTP parameters.
• Flexible configuration of limits depending on traffic parameters.
• Limit for single requests or a group of requests.
• Dry Run mode for rule testing and traffic analysis.
• ARL logging.

You can configure ARL using profiles. A profile consists of rules that impose limits on requests of a certain type. ARL uses these rules to analyze incoming HTTP requests and blocks them when their number exceeds the specified limits.

An ARL profile is connected to a security profile. ARL rules are applied to the traffic that has already been through the security profile's rules check. This makes it possible to analyze only the allowed instead of all incoming traffic and makes the ARL module more fault tolerant.

For more information about connecting to a security profile, see Getting started with an ARL profile.

An ARL rule has these settings available:

• Traffic conditions
• Request counting

Traffic conditionsTraffic conditions

An ARL rule may impose a limit on incoming HTTP requests for all traffic or traffic satisfying certain conditions.

Conditions are defined by the following parameters:

• IP: IP address, address range, or address region of clients subject to the rule.
• Request path: Path or a portion of the path the request was sent to.
• Host: Domain name the request was sent to.
• HTTP method: Method or set of methods the request belongs to.
• HTTP header: Request header parameters.
• Cookie: String in cookie files.

Request countingRequest counting

You can count the requests for the limit purposes in one of the following ways:

• Counting each request individually.
• Grouping requests by a certain attribute and limiting the number of groups.

You can group requests:

• Automatically based on the Request path, HTTP method, IP address, Region, and Host attributes.

• Based on key match in the Query params, HTTP header, and HTTP cookie attributes.

  You can configure flexible match/no match conditions for the parameters you specify for traffic. You can look for case-sensitive or case-insensitive string matches. Parameters can be represented by single values, ranges, or regular expressions.

You can also select a time interval from 1 second to 60 minutes.

All requests in excess of the limit received within the specified time interval will be blocked. In which case the client will get the 429 error.

You can use the Logging only (Dry run) mode to calculate limits and test ARL rules. Requests will not be blocked in this mode. This allows you to evaluate backend capabilities and find the optimum limit values.

See alsoSee also

• Getting started with an ARL profile