Welcome! Log In Create A New Profile

Advanced

Re: nginx directives geo and map behind proxy

Francis Daly
March 21, 2019 07:12PM
On Mon, Mar 18, 2019 at 09:49:05AM -0400, gogan wrote:

Hi there,

> 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!

Good that you have a working setup.

> A trifle still ... is set
>
> limit_req_status 429;
> limit_conn_status 429;
>
> But in access.log I get 503, why?

It works for me -- I get 429 in access.log.

Can you show a small but complete config file and test requests that
demonstrate the problem?

f
--
Francis Daly francis@daoine.org
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
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: 183
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