search
HomeOperation and MaintenanceNginxHow to implement Nginx limit request rate configuration

How to implement Nginx limit request rate configuration

How to implement Nginx limit request rate configuration

Nginx is a high-performance web server that can limit and control requests through configuration. In practical applications, in order to protect server resources, it is often necessary to limit the request rate. This article will introduce how to implement request rate limiting in Nginx.

1. Use the HttpLimitReqModule module

Nginx provides the HttpLimitReqModule module, which can be used to limit the request rate. Before starting the configuration, you need to ensure that the HttpLimitReqModule module has been installed.

  1. Edit Nginx configuration file

Open the Nginx configuration file, usually located at /etc/nginx/nginx.conf, find the http section, and add the following configuration:

http {
    ...
    limit_req_zone $binary_remote_addr zone=one:10m rate=1r/s;

    server {
        ...
    }
}

limit_req_zone is used to define the name and size of the restricted area, and $binary_remote_addr indicates using the client's IP address as the restricted keyword. zone=one:10m means using a restricted area named one with a size of 10MB. rate=1r/s means that the request rate is limited to 1 per second.

  1. Configuring request limits

Where request limits are required, add the limit_req directive to limit the request rate. For example, to limit the request rate to 10 requests/second, you can add the following configuration in the server segment: The

location / {
    limit_req zone=one burst=5;
    ...
}

limit_req directive is used to apply the request limit, the zone parameter specifies the name of the restriction zone used, and the burst parameter specifies the same time Number of requests processed. The above configuration indicates that if the number of requests exceeds 10/second, a 503 error will be returned.

  1. Reload Nginx configuration

After completing the configuration, you need to reload the Nginx configuration to make it effective. You can use the following command to check and reload the configuration:

$ nginx -t    # 检查配置是否正确
$ nginx -s reload    # 重新加载配置

2. Use the ngx_http_limit_req_module module

In addition to the HttpLimitReqModule module, you can also use the ngx_http_limit_req_module module to limit the request rate. This module provides more flexible configuration options.

  1. Edit Nginx configuration file

Open the Nginx configuration file, find the http segment, and add the following configuration:

http {
    ...
    limit_req_zone $binary_remote_addr zone=one:10m rate=1r/s;
    
    server {
        ...
    }
}

This configuration is the same as the HttpLimitReqModule module, A restricted area named one is defined, with a size of 10MB and a request rate limit of 1/second.

  1. Configuring request limits

Where request limits are required, add the limit_req directive to limit the request rate. For example, to limit the request rate to 10 requests/second, you can add the following configuration in the server segment: The

location / {
    limit_req zone=one burst=5;
    ...
}

limit_req directive is used to apply the request limit, the zone parameter specifies the name of the restriction zone used, and the burst parameter specifies the same time Number of requests processed.

  1. Reload Nginx configuration

After completing the configuration, you need to reload the Nginx configuration to make it effective. You can use the following commands to check and reload the configuration.

$ nginx -t    # 检查配置是否正确
$ nginx -s reload    # 重新加载配置

3. Use lua scripts to extend request limits

Nginx also supports the use of lua scripts to extend request limits. By writing custom Lua scripts, more flexible and complex request limiting strategies can be implemented.

  1. Install the lua module

First, you need to make sure that the Nginx lua module has been installed.

  1. Write lua script

In the Nginx configuration file, add the following configuration:

http {
    ...
    lua_shared_dict limit_req_store 10m;
    
    server {
        ...
        
        location / {
            access_by_lua_block {
                local limit_req = require "resty.limit.req"
                local lim, err = limit_req.new("limit_req_store", 1, 1)
                if not lim then
                    ngx.log(ngx.ERR, "failed to instantiate a resty.limit.req object: ", err)
                    return ngx.exit(500)
                end
                local key = ngx.var.binary_remote_addr
                local delay, err = lim:incoming(key, true)
                if not delay then
                    if err == "rejected" then
                        return ngx.exit(503)
                    end
                    ngx.log(ngx.ERR, "failed to limit req: ", err)
                    return ngx.exit(500)
                end
                if delay >= 0.001 then
                    ngx.sleep(delay)
                end
            }
            ...
        }
    }
}

This configuration uses the lua_shared_dict directive to define a limit_req_store Shared memory area, size is 10MB.

  1. Reload Nginx configuration

After completing the configuration, reload the Nginx configuration to make it effective.

4. Summary

This article introduces three ways to implement Nginx request rate limit, namely using the HttpLimitReqModule module, ngx_http_limit_req_module module and lua script. Through appropriate configuration and restriction policies, server resources can be effectively protected and malicious requests can be prevented from causing excessive load on the server. In actual applications, you can choose an appropriate method to limit the request rate according to specific needs.

The above is the detailed content of How to implement Nginx limit request rate configuration. For more information, please follow other related articles on the PHP Chinese website!

Statement
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Using NGINX: Optimizing Website Performance and ReliabilityUsing NGINX: Optimizing Website Performance and ReliabilityMay 09, 2025 am 12:19 AM

NGINX can improve website performance and reliability by: 1. Process static content as a web server; 2. forward requests as a reverse proxy server; 3. allocate requests as a load balancer; 4. Reduce backend pressure as a cache server. NGINX can significantly improve website performance through configuration optimizations such as enabling Gzip compression and adjusting connection pooling.

NGINX's Purpose: Serving Web Content and MoreNGINX's Purpose: Serving Web Content and MoreMay 08, 2025 am 12:07 AM

NGINXserveswebcontentandactsasareverseproxy,loadbalancer,andmore.1)ItefficientlyservesstaticcontentlikeHTMLandimages.2)Itfunctionsasareverseproxyandloadbalancer,distributingtrafficacrossservers.3)NGINXenhancesperformancethroughcaching.4)Itofferssecur

NGINX Unit: Streamlining Application DeploymentNGINX Unit: Streamlining Application DeploymentMay 07, 2025 am 12:08 AM

NGINXUnit simplifies application deployment with dynamic configuration and multilingual support. 1) Dynamic configuration can be modified without restarting the server. 2) Supports multiple programming languages, such as Python, PHP, and Java. 3) Adopt asynchronous non-blocking I/O model to improve high concurrency processing performance.

NGINX's Impact: Web Servers and BeyondNGINX's Impact: Web Servers and BeyondMay 06, 2025 am 12:05 AM

NGINX initially solved the C10K problem and has now developed into an all-rounder who handles load balancing, reverse proxying and API gateways. 1) It is well-known for event-driven and non-blocking architectures and is suitable for high concurrency. 2) NGINX can be used as an HTTP and reverse proxy server, supporting IMAP/POP3. 3) Its working principle is based on event-driven and asynchronous I/O models, improving performance. 4) Basic usage includes configuring virtual hosts and load balancing, and advanced usage involves complex load balancing and caching strategies. 5) Common errors include configuration syntax errors and permission issues, and debugging skills include using nginx-t command and stub_status module. 6) Performance optimization suggestions include adjusting worker parameters, using gzip compression and

Nginx Troubleshooting: Diagnosing and Resolving Common ErrorsNginx Troubleshooting: Diagnosing and Resolving Common ErrorsMay 05, 2025 am 12:09 AM

Diagnosis and solutions for common errors of Nginx include: 1. View log files, 2. Adjust configuration files, 3. Optimize performance. By analyzing logs, adjusting timeout settings and optimizing cache and load balancing, errors such as 404, 502, 504 can be effectively resolved to improve website stability and performance.

Deploying Applications with NGINX Unit: A GuideDeploying Applications with NGINX Unit: A GuideMay 04, 2025 am 12:03 AM

NGINXUnitischosenfordeployingapplicationsduetoitsflexibility,easeofuse,andabilitytohandledynamicapplications.1)ItsupportsmultipleprogramminglanguageslikePython,PHP,Node.js,andJava.2)Itallowsdynamicreconfigurationwithoutdowntime.3)ItusesJSONforconfigu

NGINX and Web Hosting: Serving Files and Managing TrafficNGINX and Web Hosting: Serving Files and Managing TrafficMay 03, 2025 am 12:14 AM

NGINX can be used to serve files and manage traffic. 1) Configure NGINX service static files: define the listening port and file directory. 2) Implement load balancing and traffic management: Use upstream module and cache policies to optimize performance.

NGINX vs. Apache: Comparing Web Server TechnologiesNGINX vs. Apache: Comparing Web Server TechnologiesMay 02, 2025 am 12:08 AM

NGINX is suitable for handling high concurrency and static content, while Apache is suitable for dynamic content and complex URL rewrites. 1.NGINX adopts an event-driven model, suitable for high concurrency. 2. Apache uses process or thread model, which is suitable for dynamic content. 3. NGINX configuration is simple, Apache configuration is complex but more flexible.

See all articles

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Atom editor mac version download

Atom editor mac version download

The most popular open source editor

SublimeText3 Linux new version

SublimeText3 Linux new version

SublimeText3 Linux latest version

mPDF

mPDF

mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

MinGW - Minimalist GNU for Windows

MinGW - Minimalist GNU for Windows

This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

SublimeText3 English version

SublimeText3 English version

Recommended: Win version, supports code prompts!