Hi there,
I'm having an issue where all my logs flag up my load-balancer IP instead of real visitor IP. This meant whenever we got a large scale attack, our load-balancers got blacklisted by ModSecurity on the servers.
I just found the option on LiteSpeed admin "Use Client IP in Header", we use Amazon Web Services and take advantage of the elastic load balancer.
There is access control on LiteSpeed but our servers only accept traffic from the load balancer so am i safe to switch the "Use Client IP in Header" setting on without having it on "Trust IP Only"? On top of this, the load-balancer only has a static hostname, the IP is dynamic.
Does this also protect us from spoofing?
Thanks in advance
I'm having an issue where all my logs flag up my load-balancer IP instead of real visitor IP. This meant whenever we got a large scale attack, our load-balancers got blacklisted by ModSecurity on the servers.
I just found the option on LiteSpeed admin "Use Client IP in Header", we use Amazon Web Services and take advantage of the elastic load balancer.
There is access control on LiteSpeed but our servers only accept traffic from the load balancer so am i safe to switch the "Use Client IP in Header" setting on without having it on "Trust IP Only"? On top of this, the load-balancer only has a static hostname, the IP is dynamic.
Does this also protect us from spoofing?
Thanks in advance