Hi Maxim, thank you for quick response. > How did you found that limit_req uses a wrong element? We don't know if this is limit_req - in reality we were just looking into logs and I guess that's what confused us. We observed those IPs and rolled back the changes as we assumed that all requests from CDN or DDOS Service were blocked. The only way to I guess to verify that our current scby malish8632 - Nginx Mailing List - English
Hi, if our HTTP block looks like below where we find IP from X-Forwarded-For using perl module it looks like zone and limit_req are not using correct variable $user_real_ip or it is reset right after logging. The nginx_access_log shows the first logged field correctly as $user_real_ip - which is first element of comma separated IP addresses in X-Forwarded-For header from different hopes. User rby malish8632 - Nginx Mailing List - English
We encountered issue with rewrite regex on Nginx - basically we have bellow rule, which would rewrite URL like http://www.domain.com/php/api_name/xxx=1/yyy=2/zzz=3.... to hit specific PHP script and would populate $_GET with list of sent parameters. For some reason any parameters after 9th will be not set in $_GET. It adds api0, api1, api2.... unset parameters. Any idea if there is a way to reby malish8632 - How to...