Allow and Deny IP's

Kaushal Shriyan kaushalshriyan at gmail.com
Wed Feb 7 16:27:04 UTC 2018


On Wed, Feb 7, 2018 at 5:32 AM, Francis Daly <francis at daoine.org> wrote:

> On Mon, Feb 05, 2018 at 11:56:04PM +0530, Kaushal Shriyan wrote:
>
> Hi there,
>
> > When i run this curl call -> curl -X GET http://13.127.165.226/ -H
> > 'cache-control: no-cache' -H 'postman-token:
> > 2494a4a7-6791-2426-cedf-d0bcaa1cd90a' -H 'x-forwarded-for:
> 12.12.12.13.11'
> >
> > Ideally the request should not be allowed and the access log should
> report
> > 403 instead of 200
>
> Why should it not be allowed?
>

Hi Francis,

In the curl request I am adding http header -H 'x-forwarded-for:
12.12.12.13.11'

curl -X GET http://13.127.165.226/ -H 'cache-control: no-cache' -H
> 'postman-token: 2494a4a7-6791-2426-cedf-d0bcaa1cd90a' -H
> 'x-forwarded-for: 12.12.12.13.11'


IP :- 12.12.12.13.11 should be denied with 403

Please let me know if i am missing anything.

Best Regards,

Kaushal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20180207/8ee2eef0/attachment.html>


More information about the nginx mailing list