Francis Daly Wrote: ------------------------------------------------------- > geo $limited { > default 0; > x.x.x.x 1; > } > > map $limited $botlimit { > 1 ''; > 0 $remote_addr; > } > That config says that requests with $remote_addr set to x.x.x.x should > not be limited, and everything else should be limited. Yes, this is how it sby gogan - Nginx Mailing List - English
Hi, thanks for the response. I try it with a short view. Situation 1) Proxy (external, myracloud) <--- Connect official way | LB/Proxy (internal) | w-1 w-2 w-3 .. w10 Situation 2) LB/Proxy (internal) <--- directly connect | w-1 w-2 w-3 .. w10 In both situations I see real client IP addresses in server lby gogan - Nginx Mailing List - English
We have a problem with mapping ip's on our nginx loadbalancer behind myracloud (proxy). In configuration file we have: set_real_ip_from x.x.x.x ... real_ip_header CF-Connecting-IP; real_ip_recursive on; In addition to map ip's: geo $limited { default 0; x.x.x.x 1; } map $limited $botlimit { 0 $remote_addr; 1 ''; } We want to limit requests with limit_req_zby gogan - Nginx Mailing List - English