


nginx whitelist configuration beyond limiting the number of connections and requests nginx apache nginx php nginx rewrite
I have written two articles before to introduce nginx_http_limit_req_module and nginx_http_limit_conn_module, which respectively limit the number of user requests and connections. The whitelist is mainly to divide some internal personnel so that they are not affected by the restrictions.
You can read the previous article first:
nginx limits the number of requests
http://blog.csdn.net/wanglei_storage/article/details/51076882
nginx limits the number of connections
http://blog.csdn.net/wanglei_storage/article/details/51076561
Module View:
tening After compilation and installation, use sbin/nginx -V to view all modules, and whitelist configuration is required geo module support.
1. geo command
Syntax: geo $variable {……}
Default value: none
Configuration section: http
Parameter introduction:
default: nginx will use this value if the client address cannot match any of the defined addresses. If CIDR is used, "0.0.0.0/0" can be used instead of default.
ranges: Define the address in the form of an address segment. This parameter must be placed first. To speed up loading of the address library, addresses should be defined in ascending order.
2. Configuration usage example:
1) Limit the number of requests
limit_req_zone: used to define the limit request zone; includes client address, zone name, shared memory, and rate.
2) Limit the number of connections
limit_conn_zone: used to define a restricted connection area; includes area name and shared memory.
3) geo mainly defines the whitelist configuration, the variable is $white_ip, and the parameters and specific values are defined in { }.
Use limit_req_whitelist at the bottom to apply the configured whitelist, where geo_var_name represents the variable name set by the geo module; and geo_var_value represents the variable value set by the geo module; all IPs in the whitelist are not subject to any restrictions.
The above introduces the whitelist configuration of nginx other than limiting the number of connections and requests, including nginx content. I hope it will be helpful to friends who are interested in PHP tutorials.

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

There are two ways to solve the Nginx cross-domain problem: modify the cross-domain response header: add directives to allow cross-domain requests, specify allowed methods and headers, and set cache time. Use CORS modules: Enable modules and configure CORS rules that allow cross-domain requests, methods, headers, and cache times.

The methods to view the running status of Nginx are: use the ps command to view the process status; view the Nginx configuration file /etc/nginx/nginx.conf; use the Nginx status module to enable the status endpoint; use monitoring tools such as Prometheus, Zabbix, or Nagios.
