Limit Traffic and Limit Rate

Rate limiting are common requirements to protect the system from unexpected traffic or malicious attacks and still provide normal services.

The following are a few common scenarios for limiting flow and rate, all of which can be implemented by adding rules to the Edge Admin console interface, and we will cover the basic operations later.

1. Limit request rate
2. Limit the number of requests per unit time
3. Delay request
4. Block client request
5. Limit response data rate
6. Limit SSL handshake rate
7. Block Source IP
8. Block IP List

Among these, the 5th action is a rule for responses, while all others are rules for requests.

The 6th action can only use the client IP address as the rate limiting key, whereas actions 1-5 can have more key options to choose from: client IP address, URI, URI parameters, or request cookies. Actions 7 and 8 will reject the specified IP at the operating system level for a certain period of time, during which all packets from that IP will be dropped.

It should be noted that all rate limit rules here are effective within the application and not across applications. This is not the same as NGINX.

For example, if a client triggers a rate limit rule for application A, that client can still access application B normally.