How to limit the speed of IP and directory under Nginx

This article introduces the relevant knowledge of "how to target IP and directory speed limit under Nginx". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

From the voting results of the topic on Nginx configuration and application details, Nginx is now the Web server second only to APache and MS IIS. Nginx's excellent high concurrency support and efficient load balancing are the reasons why we choose it. But sometimes we wish it could do more. This article will show you how to limit the speed of IP and directories under Nginx, which is also a common requirement in certain application scenarios.

Nginx can limit speed through the HTTPLimitZoneModule and HTTPCoreModule directories.

Example:

Limit_zone one $binary_remote_addr 10m; location / {limit_conn one 1; limit_rate 100k;}

Description:

Limit_zone, which defines a container for storing session state for each IP. In this example, a 10m container is defined, which can handle 320000 session according to 32bytes/session.

Then set it for the directory.

Limit_conn one 1

Is to limit each IP to one connection.

Limit_rate 100k

The speed limit is 100k per connection. Note that this is a speed limit for connections, not for IP. If an IP allows two concurrent connections, then the IP is the speed limit limit_rate x 2.

This is the end of the content of "how to target IP and directory speed limit under Nginx". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!