Cloudflare reports 520 on a 444 response from server
Hi
We have installed a very comprehensive list of nginx rules to block aggressive bots and malicious scanners, and in doing so our server responds with a code 444 "No response" for such requests.
This is very common to respond with 444 on malicious requests because it is very light on nginx and also to hide any type of potential response that could assist the malicious users.
Cloudflare should in my opinion respond with 444 as well not 520.
Any ideas if that's something we can modify or not?
We have installed a very comprehensive list of nginx rules to block aggressive bots and malicious scanners, and in doing so our server responds with a code 444 "No response" for such requests.
This is very common to respond with 444 on malicious requests because it is very light on nginx and also to hide any type of potential response that could assist the malicious users.
Cloudflare should in my opinion respond with 444 as well not 520.
Any ideas if that's something we can modify or not?
