Welcome! Log In Create A New Profile

Advanced

Re: nginx directives geo and map behind proxy

March 18, 2019 09:49AM
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 should work.

> Does myracloud set the Cloudflare header?

Yes.

> and make some requests for /iptest, which lines show the address
> x.x.x.x
> and which lines show the real client IP address?
>

With myracloud CF-Connecting-IP and remote_addr are set to client ip and real remote is myracloud ip. botlimit is set to remote_addr in general and to x.x.x.x if hits in geo given ip address. So far as I expected and now it works. I don't know why, but I have a better understanding because of your help, thanks!

A trifle still ... is set

limit_req_status 429;
limit_conn_status 429;

But in access.log I get 503, why?
Subject Author Posted

nginx directives geo and map behind proxy

gogan March 12, 2019 06:22AM

Re: nginx directives geo and map behind proxy

Francis Daly March 14, 2019 02:34PM

Re: nginx directives geo and map behind proxy

gogan March 15, 2019 10:34AM

Re: nginx directives geo and map behind proxy

Francis Daly March 16, 2019 05:34AM

Re: nginx directives geo and map behind proxy

gogan March 18, 2019 09:49AM

Re: nginx directives geo and map behind proxy

Francis Daly March 21, 2019 07:12PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 153
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready