Nesting mod_evasive directives within Files, Location, ...
2 posts
• Page 1 of 1
Nesting mod_evasive directives within Files, Location, ...
Is it possible to nest mod_evasive directives within Files or Location functions? I would like to know if one can enable mod_evasive only for certain URI's, like /wp-login /administrator, and so on.
For example (might not be syntactical correct):
WordPress plugins like VisualComposor don't work with mod_evasive very well, so I'd like to be able to secure only login URL's.
When this is not possible, it would make a nice feature for a future release...
For example (might not be syntactical correct):
- Code: Select all
<VirtualHost *:80>
LoadModule evasive_module modules/mod_evasive.so
<IfModule evasive_module>
#<Files wp-login\.php>
<Location /wp-admin>
DOSHashTableSize 2048
DOSPageCount 20
DOSSiteCount 150
DOSPageInterval 2
DOSSiteInterval 1
DOSBlockingPeriod 120
</Location>
#</Files>
</IfModule>
</VirtualHost>
WordPress plugins like VisualComposor don't work with mod_evasive very well, so I'd like to be able to secure only login URL's.
When this is not possible, it would make a nice feature for a future release...
Re: Nesting mod_evasive directives within Files, Location, .
Hello,
As is said in our docs (http://www.helicontech.com/ape/doc/mod_evasive.htm),
mod_evasive directives can only be used in httpd.conf and <VirtualHost> sections - this is by design as it is supposed to protect the entire server.
As is said in our docs (http://www.helicontech.com/ape/doc/mod_evasive.htm),
mod_evasive directives can only be used in httpd.conf and <VirtualHost> sections - this is by design as it is supposed to protect the entire server.
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 3 guests