Welcome! Log In Create A New Profile

Advanced

Re: upstream 429 and non-idempotent request

Maxim Dounin
June 08, 2017 11:20AM
Hello!

On Thu, Jun 08, 2017 at 01:10:25AM -0700, Frank Liu wrote:

> In case of upstream returning 429, I'd like to have nginx retry next
> upstream server. Since nginx by default won't retry non-idempotent
> requests, how do I force nginx to retry when receiving 429? I imagine this
> should be the default behavior anyway, or does nginx not care about
> returning code and will never retry non-idempotent?

Non-idemportent requests are not retried as long as the request is
already sent, regardless of a particular error. If you want nginx
to retry non-idempotent requests, you can do so with
"proxy_next_upstream non-idempotent;", see
http://nginx.org/r/proxy_next_upstream.

--
Maxim Dounin
http://nginx.org/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

upstream 429 and non-idempotent request

Frank Liu June 08, 2017 04:12AM

Re: upstream 429 and non-idempotent request

Maxim Dounin June 08, 2017 11:20AM

Re: upstream 429 and non-idempotent request

Frank Liu June 08, 2017 12:56PM

Re: upstream 429 and non-idempotent request

Maxim Dounin June 13, 2017 12:32PM

Re: upstream 429 and non-idempotent request

Frank Liu June 13, 2017 05:42PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 252
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