Re: Block countries - Nginx

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

Re: Block countries - Nginx

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

Re: Block countries - Nginx

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

Re: Block countries - Nginx

If you can dump your http traffic you will probably see a headers with names like: X-Real-IP X-Forwarded-For Sent from my iPhone > On May 23, 2018, at 11:25 PM, Frank Liu wrote: > > Since only load balancer sees the client IP, it has to pass that information > to nginx.

Re: Block countries - Nginx

Since only load balancer sees the client IP, it has to pass that information to nginx. You need to talk to your LB engineer and depending on the type of LB, there are different ways to do that. Once the information is passed to nginx, nginx will expose it as a variable, which can then be used by

Re: Block countries - Nginx

How can I get the client IP address if the request is coming through load balancer or Proxy and pass it to default nginx geoip module to block it based on the Country. On Tue, May 22, 2018, 4:45 PM Frank Liu wrote: > Instead of the default nginx geoip module , I suggest you

Re: Block countries - Nginx

Instead of the default nginx geoip module , I suggest you switch to third party geoip2 module for two reasons: 1) maxmind deprecated geoip1 db. 2)geoip2 module can do what you wanted, and the geo lookup can be based on any variables, such as $http_x_forwarded_for Frank On Mon, May 21, 2018 at

Re: Block countries - Nginx

On 21/05/2018 11:49, Sathish Kumar wrote: > Hi All, > > I have a requirement to block certain countries coming to our website. I > managed to achieved it using the ngx_http_geoip_module. I have a problem > now, if the request comes through Amazon API Gateway, how can I read the > X-forwarded-for

Re: Block countries - Nginx

Hello, if you have access to this load balancer, the best way would be to block it there. This also drop down the system load on your load balancer. Am 22.05.2018 um 03:37 schrieb Sathish Kumar: > Hi All, > > Is there a way, I can block the clients which is coming through load > balancer using

Re: Block countries - Nginx

Hi All, Is there a way, I can block the clients which is coming through load balancer using http geo ip module nginx. Currently, I can block the clients which is not coming through load balancer or api gateway by geo ip module. On Mon, May 21, 2018, 2:02 PM basti

Re: Block countries - Nginx

hello, the way to block ip's can also be used for PTR records, I think. Also as wildcard. On 21.05.2018 05:49, Sathish Kumar wrote: > Hi All, > > I have a requirement to block certain countries coming to our website.  > I managed to achieved it using the ngx_http_geoip_module. I have a > problem

Block countries - Nginx

Hi All, I have a requirement to block certain countries coming to our website. I managed to achieved it using the ngx_http_geoip_module. I have a problem now, if the request comes through Amazon API Gateway, how can I read the X-forwarded-for header or block these request too. nginx.conf map