Dont.
You should let every tier do it’s job. Just because nginx has geoid
functionality doesn’t mean that you should use it.
If you are lucky enough to have hardware load balancer in front of nginx then
do the blocking there, so you reduce the
load on your nginx. The Golden Rule of keeping websi
On Thu, May 24, 2018 at 09:57:24PM +0800, Sathish Kumar wrote:
Hi there,
> The client is already sending the X-Forwarded-For but when it received on
> server it has multiple ips, how we can filter only the 1st IP and pass it
> to geo ip module to block the IP based on Country.
Does http://nginx.
Hi everyone, I'm brand new to nginx and maybe you can help me with a
problem I'm having.
I was formerly using "pound" as a front-end for my web servers, but I'm
switching to nginx because pound has some problems and isn't supported.
Problem is, switching to nginx has disabled "Keep-Alive". Pound
I need some thoughts on this problem.
I am load balancing upstream servers, two are IIS servers on VMs and one is an
Azure App Service (PaaS) web app. During deployment the apps are shut down and
reloaded. The problem is that the Azure web app returns a 403 when it is shut
down, so Nginx serves
Hi,
The client is already sending the X-Forwarded-For but when it received on
server it has multiple ips, how we can filter only the 1st IP and pass it
to geo ip module to block the IP based on Country.
On Thu, May 24, 2018, 11:25 AM Frank Liu wrote:
> Since only load balancer sees the client IP
