3 ms·
Not easily on a static server and not without the risk of annoying an actual real human listener! If you look at the "Defences" section: https://www.earth.org.
by DamonHD 2y ago
Not easily on a static server and not without the risk of annoying an actual real human listener!
If you look at the "Defences" section: https://www.earth.org.uk/RSS-efficiency.html#Hints https://www.earth.org.uk/RSS-efficiency.html#Hints you'll see there are some things that can be done, such as randomly rejecting a large fraction of requests that don't allow compression (gzip is madly effective on many feed files: it's rude for a client not to allow it). But all these measures take effort to set up, and don't stop the bad bots making the request 100s of times too often. Just responding to each stupid request forces a flurry of packets and wakes up and uses CPU...