Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

There are many articles explaining many ways to attack webservers (generic or specific) and even listing general rules for mitigating such attacks, e.g.:

  • Do not accept connections with abnormally small advertised window sizes
  • Drop connections that send request longer than X seconds
  • Send RST or FIN after 30 seconds when client can't accept the data due to a full receive window
  • Limit number of connections from same IP
  • Drop more than X repetitive headers (such as Range)
  • etc etc...

Are there ready to use, tested on prod configuration examples specific to webserver (we use Apache and Nginx) or system wide (Linux) that cover most common attacks?

share|improve this question
up vote 0 down vote accepted

This link is a good one. As always, read it very carefully and do your homework - not all of this may suit your environment.

share|improve this answer
Be careful. Some of the advice given in that article is plain bad, such as the advice which blocks the Bing search engine. – Michael Hampton Sep 14 '12 at 11:58
Hence the note about doing your homework. Your statement - that blocking Bing is bad - is exactly the broad brush advice I warn against above. All of this is case by case, and you need to evaluate it against your needs. – mcauth Sep 18 '12 at 13:12

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.