Heh, thanks for the tip. Of course, I've tried to apply MaxConnPerIP to particular location used by affected virtual host, with no success. Please check my previous reply that contains my explanations and assumption about the reasons why mod-limitipconn seems to be useless ;) -----Ursprüngliche Nachricht----- Von: William A. Rowe, Jr. [mailto:wrowe@xxxxxxxxxxxxx] Gesendet: Dienstag, 14. April 2009 22:15 An: users@xxxxxxxxxxxxxxxx Betreff: Re: Connection flood: how to protect? Kanstantin Reznichak wrote: > Hello, > > Thank you for reply. Unfortunately, mod-limitipconn seems to act too late. > After installing and enabling it: > <Location /> > MaxConnPerIP 15 > </Location> Read what you wrote. Location / - you are asking apache to do nothing until it has torn apart the request and figured out that it applies to a particular location. You got what you asked for. Don't you want to limit that Globally or in the physical IP VirtualHost scope? --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|