Found some answers. 1. Because I am not familiar with HTML, I have found out that it is the proxy webpage, which requested images from a third-party website. The website will verify the referer, but can allow the referer to be empty. Prohibit the use of referer when requesting, and the problem will be solved. Referrer Policy Here you can see the introduction of referrer. Well, referrer can be banned, so we can do the simplest thing, ban referrer globally 2. So here it is
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It has nothing to do with nginx. This request is simply your nginx and you have no control over it.
Found some answers.
1. Because I am not familiar with HTML, I have found out that it is the proxy webpage, which requested images from a third-party website. The website will verify the referer, but can allow the referer to be empty.
Prohibit the use of referer when requesting, and the problem will be solved.
Referrer Policy Here you can see the introduction of referrer.
Well, referrer can be banned, so we can do the simplest thing, ban referrer globally
2. So here it is
3. Here
I saw an article about how-to-add-a-response-header-on-nginx-when-using-proxy-pass,
4. So now I just use add_header or more_set_header to add a prohibited referrer.
I am not familiar with HTML, how should I add it?