Allow and Deny IP's

Jason Whittington Jason.Whittington at
Wed Feb 7 20:11:57 UTC 2018

I find that add_header always works well to verify that the location is being chosen the way you think.

Try something like

   add_header X-NGINX-Route <foobar> always;

to some of your location blocks and specify different distinct values for <foobar>.

Then in your browser you can use F12 tools to verify that you are getting back the header you expected.


-----Original Message-----
From: nginx [mailto:nginx-bounces at] On Behalf Of Ph. Gras
Sent: Wednesday, February 07, 2018 12:29 PM
To: nginx at
Subject: [IE] Re: Allow and Deny IP's

Hi Francis,

>> location ~* wp-login\.php$ {
>> - - [05/Feb/2018:21:36:12 +0100] "GET /wp-login.php HTTP/1.1" 200 1300 "-" "Mozilla/5.0 (Windows NT 6.0; rv:34.0) Gecko/20100101 Firefox/34.0"
>> Me too :-(
> Have you any reason to believe that this location is used to handle this request?

Yes, and this especially since before, it worked as expected :-(

> $ nginx -T | grep 'server\|location'
> will possibly give a useful hint in that direction.

# nginx -T | grep ""
nginx: invalid option: "T"

Is something missing ?

# apt-show-versions | grep nginx
nginx:all/jessie 1.6.2-5+deb8u5 uptodate nginx-common:all/jessie 1.6.2-5+deb8u5 uptodate nginx-full:amd64/jessie 1.6.2-5+deb8u5 uptodate python-certbot-nginx:all/jessie-backports 0.10.2-1~bpo8+1 uptodate

Thank your for your help,

Ph. Gras
nginx mailing list
nginx at

This message contains proprietary information from Equifax which may be confidential. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e-mail postmaster at Equifax® is a registered trademark of Equifax Inc. All rights reserved.

More information about the nginx mailing list