What are the nginx-naxsi whitelist rules?
Whitelist rule syntax:
basicrule wl:id [negative] [mz:[$url:target_url]|[match_zone]|[$args_var:varname]|[$ body_vars:varname]|[$headers_var:varname]|[name]]
Which interception rules will enter Whitelist | |
Add all interception rules to the whitelist | |
Add the interception rule with ID 42 to the whitelist | |
Add the interception rule with IDs 42, 41 and 43 to the whitelist | |
Add all interception rules to the whitelist, except the interception rule with id 42 |
get’s entire parameters, such as: foo=bar&in= | |
Get the parameter name of the parameter, such as foo and in in foo=bar&in= | |
The parameter name of the regular matching get parameter | |
The entire http protocol header | |
The name of the http protocol header | |
The name of the regular matching http protocol header | |
The entire parameter content of post | |
The parameter name of post parameter | |
Parameter name of the regular matching post parameter | |
#url (before ?) | |
Regular matching url (before ?) | |
File name (the file name uploaded when uploading a file in post) |
Take rule #1000 as an example: Rule #1000 filters out select, update, delete, insert Rules for sql keywords
Description | |
Completely disable interception rule #1000 in this sub-rule. Because there is no specified area, all are added to the whitelist. | |
Disable interception rules in all get parameter values named foo#1000 |
Requests like http://mike.hi-linux.com/?foo=select * from demo will not be filtered. |
In the get request with url /bar Parameter disable interception rule #1000 |
The following similar requests will not be filtered: http://mike.hi-linux.com/bar?my=select * from demohttp:// mike.hi-linux.com/bar?from=weibo |
at Disable interception rules for all parameter names (just names, not including parameter values) in all get requests #1000 |
The following requests will not be filtered: http://mike.hi-linux .com/bar?from=weibo The following requests will be filtered: http://mike.hi-linux.com/bar?foo=select Because select It is a parameter value and is not in the whitelist range. |
Disable all interception rules for URLs that match ^/upload/(.*).(.*)$ regular rules in all requests |
Similar to http://mike.hi-linux.com/upload The /select.db request will not be filtered (it would have triggered the #1000 interception rule). |
The above is the detailed content of What are the nginx-naxsi whitelist rules?. For more information, please follow other related articles on the PHP Chinese website!

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

To allow the Tomcat server to access the external network, you need to: modify the Tomcat configuration file to allow external connections. Add a firewall rule to allow access to the Tomcat server port. Create a DNS record pointing the domain name to the Tomcat server public IP. Optional: Use a reverse proxy to improve security and performance. Optional: Set up HTTPS for increased security.

Steps to run ThinkPHP Framework locally: Download and unzip ThinkPHP Framework to a local directory. Create a virtual host (optional) pointing to the ThinkPHP root directory. Configure database connection parameters. Start the web server. Initialize the ThinkPHP application. Access the ThinkPHP application URL and run it.

To solve the "Welcome to nginx!" error, you need to check the virtual host configuration, enable the virtual host, reload Nginx, if the virtual host configuration file cannot be found, create a default page and reload Nginx, then the error message will disappear and the website will be normal show.

There are five methods for container communication in the Docker environment: shared network, Docker Compose, network proxy, shared volume, and message queue. Depending on your isolation and security needs, choose the most appropriate communication method, such as leveraging Docker Compose to simplify connections or using a network proxy to increase isolation.

To register for phpMyAdmin, you need to first create a MySQL user and grant permissions to it, then download, install and configure phpMyAdmin, and finally log in to phpMyAdmin to manage the database.

Server deployment steps for a Node.js project: Prepare the deployment environment: obtain server access, install Node.js, set up a Git repository. Build the application: Use npm run build to generate deployable code and dependencies. Upload code to the server: via Git or File Transfer Protocol. Install dependencies: SSH into the server and use npm install to install application dependencies. Start the application: Use a command such as node index.js to start the application, or use a process manager such as pm2. Configure a reverse proxy (optional): Use a reverse proxy such as Nginx or Apache to route traffic to your application

Converting an HTML file to a URL requires a web server, which involves the following steps: Obtain a web server. Set up a web server. Upload HTML file. Create a domain name. Route the request.

Troubleshooting steps for failed phpMyAdmin installation: Check system requirements (PHP version, MySQL version, web server); enable PHP extensions (mysqli, pdo_mysql, mbstring, token_get_all); check configuration file settings (host, port, username, password); Check file permissions (directory ownership, file permissions); check firewall settings (whitelist web server ports); view error logs (/var/log/apache2/error.log or /var/log/nginx/error.log); seek Technical support (phpMyAdmin
