In the error.log log, nginx found entries:

2016/10/19 09:19:36 [error] 30110 # 0: * 222886 open () "/home/public/images/xxx.jpg" failed (2: No such file or directory), client: 123.123.123.123 , server: site.ru, request: "GET /images/xxx.jpg HTTP / 1.1", host: "site.ru", referrer: " http://site.ru/ "

Someone bot requested a file 40 times per second for 12 minutes. The images directory does not exist. The file xxx.jpg exists, but is in the img directory. The presence of the img directory for the site visitor is obvious, the path is written in the address bar of the browser when opening pictures. That is, the incorrect images directory was pointed out to the bot intentionally.

What is the point of launching such a request by a bot? That is, more interested in what the bot wanted to get?

  • there are different options - from the banal someone wanted to download pictures from the site, but a little missed in the ways, well, it doesn’t happen to anyone, to strange ones - for example, this is a bug in the nginx configs and as a result the browser redirected here. I would look at the ip and see if this is the target audience or not. If not, you can just ban. - KoVadim

0