


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

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

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 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.

Docker container startup steps: Pull the container image: Run "docker pull [mirror name]". Create a container: Use "docker create [options] [mirror name] [commands and parameters]". Start the container: Execute "docker start [Container name or ID]". Check container status: Verify that the container is running with "docker ps".

You can query the Docker container name by following the steps: List all containers (docker ps). Filter the container list (using the grep command). Gets the container name (located in the "NAMES" column).

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.

Create a container in Docker: 1. Pull the image: docker pull [mirror name] 2. Create a container: docker run [Options] [mirror name] [Command] 3. Start the container: docker start [Container name]

The methods that can query the Nginx version are: use the nginx -v command; view the version directive in the nginx.conf file; open the Nginx error page and view the page title.

How to configure an Nginx domain name on a cloud server: Create an A record pointing to the public IP address of the cloud server. Add virtual host blocks in the Nginx configuration file, specifying the listening port, domain name, and website root directory. Restart Nginx to apply the changes. Access the domain name test configuration. Other notes: Install the SSL certificate to enable HTTPS, ensure that the firewall allows port 80 traffic, and wait for DNS resolution to take effect.

When the Nginx server goes down, you can perform the following troubleshooting steps: Check that the nginx process is running. View the error log for error messages. Check the syntax of nginx configuration. Make sure nginx has the permissions you need to access the file. Check file descriptor to open limits. Confirm that nginx is listening on the correct port. Add firewall rules to allow nginx traffic. Check reverse proxy settings, including backend server availability. For further assistance, please contact technical support.
