> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/security/rate-limiting/configure-rate-limiting.md).
# 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](https://cloud.medianova.com).
## Configure Rate Limiting
{% stepper %}
{% step %}
#### Open Rate Limiting
Open the CDN Resource that you want to configure, select **Security**, and then select **Rate limiting**.
{% endstep %}
{% step %}
#### Enable Rate Limiting
Turn on **Rate Limiting**.
{% endstep %}
{% step %}
#### 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.
{% hint style="info" %}
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.
{% endhint %}
{% endstep %}
{% step %}
#### 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.
{% hint style="info" %}
Burst capacity does not increase the configured request rate. It provides temporary tolerance for short traffic spikes above the configured rate.
{% endhint %}
{% endstep %}
{% step %}
#### 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**.
{% endstep %}
{% step %}
#### 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.
{% endstep %}
{% step %}
#### Save the Configuration
Select **Save** in the pending changes bar.
Review the pending changes and confirm the configuration.
{% endstep %}
{% endstepper %}
## 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**](/products/performance-cdn/static-content-delivery/advanced-configuration/page-rules.md).
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.
{% hint style="info" %}
IP whitelisting is not available for Page Rule-based Rate Limiting.
{% endhint %}
{% hint style="info" %}
For configuration steps and examples, see [Path & Extension Based Rate Limiting](/products/performance-cdn/static-content-delivery/advanced-configuration/page-rules/page-rules-settings/path-and-extension-based-rate-limiting.md).
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://clients.medianova.com/products/security/rate-limiting/configure-rate-limiting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
