Re: [no subject]

[lists]

When I blocked IP space in the past using Nginx, it seemed to parse the request anyway. That is the blocking was very low level. The code from the OP will add to the "regular" 403s, which I create by hot link detection. I look at the 403s to insure it isn't some other bug (AKA my coding), so the IP space blocking could really increase the error report size. It is a bit off topic, but you really should look at hit linkers to determine if the website is of low reputation (spam or porn).  Back to the OPs request, unless the OP lives in a data center, the question makes it appear to me like they are using a home server. I did that in the 90s, but the internet is a really nasty place to have your home IP internet facing. These VPSs are really cheap. I doubt I will ever use a hosting company again  From: nginx@nginx.org Sent: April 13, 2019 9:36 AM To: nginx@nginx.org Reply-to: nginx@nginx.org Cc: peter_bo...@me.com Subject: Re: [no subject] I don’t think it’s a dumb question at all. It’s a very astute question. My experience of protecting a high traffic retail website  from a foreign state-sponsored DDOS was that doing IP blocking on a hardware load bakancer in front of the nginx tier was the difference between the site bring available and the site being down on an unusually busy day. The economic impact of having both nginx and the load balancer working in concert saved millions of dollars revenue in one busy day. The load balancer (well it was the WAF module in an F5 BigIP)  was doing what could have equally been done in a firewall. With F5’s acquisition of nginx we might see innovative ways of combining the best hardware and software ADC solutions to build rock solid websites. Anything you can do to protect your backend helps your website stay alive, whether it’s browser caching, CDN, firewall, hardware load balancer, before getting to nginx. Then if nginx has intelligent caching rules you can build a site that sustained enormous bursts of traffic and stays up. Nginx is like a Swiss Army knife of http that can do so many different things - but that doesn’t mean it’s right to expect that it does everything. Peter Sent from my iPhone On Apr 12, 2019, at 10:57 PM, lists <li...@lazygranch.com> wrote: Perhaps a dumb question, but if all you are going to do is return a 403, why not just do this filtering in the firewall by blocking the offending IP space. Yeah I know a server should always have some response, but it isn't like you would be the first person to just block entire countries. (I don't do this on 80/443, but I do block most email ports outside the US.)  The only reason I mention this is Nginx blocking is more CPU intensive than the firewall.  On a small VPS, you might notice the difference in loadomg. From: softwareinfo...@gmail.com Sent: April 12, 2019 7:24 PM To: nginx@nginx.org Reply-to: nginx@nginx.org Subject: Hi All I have implemented GEO IP blocking which is working just fine. I have the settings you see below.       map $geoip_country_code $country_access {         "US"    0;         default 1;     }       server {          if ($country_access = '1') {          return 403;          }   I notice though that in the logs, the internal IP Addresses are not tagged with a country code so internal subnets are getting blocked. Would the correct solution be to enter the subnets manually such as this config below? Or is there a better solution? Oh by the way, I did try this below and it didn’t work. Trying to keep the Geographical blocking but allow some IP ranges. Any ideas on how to do this? Any help would be appreciated.     map $geoip_country_code $country_access {         "US"    0;        ‘192.168.1.0/24’ 0;         default 1;     }     Regards SI     _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx