How to use nginx to prevent hotlinking
With the popularity of the Internet, more and more websites provide external link functions for pictures, videos and other resources. However, this external link function is easy to be stolen. Hotlinking means that other websites use pictures, videos and other resources on your website to directly display these resources on their own website through the reference address instead of downloading them to their own server. In this way, hotlink websites can use your website's traffic and bandwidth resources for free, which wastes resources and affects website speed.
To address this problem, Nginx can be used to prevent hotlinking. Nginx is a common web server and reverse proxy server, and it also has a good effect in preventing hot links. Next we will introduce how to use Nginx to prevent hotlinking.
Step 1: Turn on the anti-hotlink module
The core module of Nginx already has anti-hotlink related functions. Before configuring Nginx, we need to first confirm whether Nginx has the anti-hotlink module enabled. If it is not enabled, you need to recompile Nginx or install the corresponding module.
Step 2: Configure anti-hotlinking rules
Nginx’s anti-hotlinking function can be implemented through the location directive in the configuration file. We need to add the following content to the Nginx virtual host configuration file:
location ~* .(gif|jpg|jpeg|png|bmp)$ { valid_referers none blocked yourdomain.com; if ($invalid_referer) { return 403; } }
The above code indicates that external links are only allowed on yourdomain.com site. If the source is not yourdomain.com, a 403 error will be returned and direct access will not be possible.
Step 3: Add whitelist
If you need to allow certain websites or IP addresses to link externally, you can add them to the whitelist. In Nginx, whitelisting can be achieved through the valid_referers directive. For example, we can add the following code to the anti-hotlinking rules in the configuration file to add a whitelist:
location ~* .(gif|jpg|jpeg|png|bmp)$ { valid_referers none blocked yourdomain.com example.com 192.168.0.1; if ($invalid_referer) { return 403; } }
In the above code, we add yourdomain.com and example.com and the IP address 192.168.0.1 Added to the whitelist, these websites can directly access your resources.
Step 4: Enable Rewrite module
Nginx’s Rewrite module can be used to rewrite URLs. We can use the Rewrite module to hide the image URL of the origin site, thereby increasing the difficulty of hotlinking. Protect website resources. We need to add the following content to the configuration file:
if ($http_referer !~ ^http://(www.)?yourdomain.com(/|$)) { return 403; }
The above code means that if the source is not your website, a 403 error will be returned. In this way, hotlinking can be effectively prevented.
Summary
The above are some methods of using Nginx to prevent hotlinking. Through these methods, we can protect our website resources, avoid wasting bandwidth and resources, and at the same time increase the security of the website. In actual applications, you need to configure and adjust it according to your own needs to ensure the effectiveness of the anti-leeching strategy.
The above is the detailed content of How to use nginx to prevent hotlinking. 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



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.

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.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

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.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

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.

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.

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.
