Configure Rate Limiting

Configure request limits, burst handling, response status codes, and IP exemptions for Dynamic CDN Resources.

Configure request rate limits for a CDN Resource to control excessive client traffic at the CDN edge.

Rate Limiting limits the rate at which clients can send requests to a CDN Resource. You can define the request rate, configure burst handling, select the response status code, and exempt specific IP addresses from the limit.

Rate Limiting is configured per CDN Resource under Security → Rate limiting in the Medianova Control Panel.

Configure Rate Limiting

1

Open Rate Limiting

Open the CDN Resource that you want to configure, select Security, and then select Rate limiting.

2

Enable Rate Limiting

Turn on Rate Limiting.

3

Set the Request Limit

Under Request limit, specify the request limit and select the time unit, such as Per Second or Per Minute.

The configured limit is evaluated continuously as a request rate rather than as a fixed request count that resets at the end of the selected time period.

For example, a limit of 100 requests per minute is distributed over time and enforced continuously. It does not allow all 100 requests to be sent at once at any point during the minute.

Set the request limit according to the normal traffic pattern of your application. A limit that is too restrictive may affect legitimate user or API traffic.

4

Select the Mode

Under Mode, select how temporary traffic spikes above the configured request rate are handled:

• None — Enforces the configured request rate without additional burst capacity.

• Burst — Allows additional requests within the configured burst capacity. Requests within the burst capacity may be delayed and processed according to the configured rate.

• Burst + No Delay — Allows requests within the configured burst capacity to pass immediately without delay.

When Burst or Burst + No Delay is selected, configure Burst to define the additional capacity available for temporary traffic spikes.

Burst capacity does not increase the configured request rate. It provides temporary tolerance for short traffic spikes above the configured rate.

5

Select the Status Code

Under Status code, select the HTTP status code returned when a request exceeds the permitted rate and available burst capacity.

For example, 429 indicates Too Many Requests.

6

Configure Whitelist IP (Optional)

Under Whitelist IP, select Exempt specific IP addresses from this limit if trusted IP addresses should bypass Rate Limiting.

Add the IP addresses that should be exempt from the configured limit.

7

Save the Configuration

Select Save in the pending changes bar.

Review the pending changes and confirm the configuration.

Path & Extension Based Rate Limiting

In addition to resource-level Rate Limiting, you can configure rate limiting rules for specific URL paths or file extensions through Page Rules.

Use Path & Extension Based Rate Limiting when different parts of your application require different request rates. For example, separate limits can be applied to sensitive routes, API paths, or specific file types.

Path- and extension-based rules use the same rate limiting behavior, including continuous rate enforcement and burst handling, but are configured separately under Page Rules.

IP whitelisting is not available for Page Rule-based Rate Limiting.

For configuration steps and examples, see Path & Extension Based Rate Limiting.