Tag Info

New answers tagged

2

Alternatively, don't use ELB but roll out your own load balancer using HAProxy. If you've been deploying your site using AWS OpsWorks, you should be aware that AWS OpsWorks supports a HAProxy-based Load Balancer Layer. Yes, preparing a HAProxy Load Balancer Layer is much more involved than simply spinning up an ELB set, but ultimately it allows you to ...


1

The original client IP is provided by ELB in the X-Forwarded-For header. You can use the X-Forwarded-For in your rewrite rules.


1

Blocking the ip's in iptables is a good plan since it will minimize the impact on your server. But the rules in iptables are there forever so you need something else to manage the expiration of the blacklist. fail2ban seems like the easy solution to this. Another problem is that the source IP's will be the internal ELB IP's so you need to do the filtering ...


1

So, here's my answer. By ispecting the return headers I noticed that Joomla! backend returns some HTTP headers when login is correct, and doesn't return them when login is invalid. e.g., the P3P header is returned after a successful login, so I just look for its length being > 0: SecAction phase:1,nolog,pass,initcol:ip=%{REMOTE_ADDR},id:5000144 ...


0

As you already answered to your question here, you should create additional configuration file and put this line in it, it will disable Atomicorp rule you you were mentioning for this user/domain only (for everyone). File : /usr/local/apache/conf/userdata/std/2/username/example.com <IfModule mod_security2.c> SecRuleRemoveById 392301 ...



Top 50 recent answers are included