proxy_next_upstream exemption for 429 "too many requests"

[Piotr Sikora]

Hey Marques,
coincidentally, I sent patches for 429 yesterday:
http://mailman.nginx.org/pipermail/nginx-devel/2016-October/009003.html
http://mailman.nginx.org/pipermail/nginx-devel/2016-October/009004.html

Best regards,
Piotr Sikora

On Wed, Oct 19, 2016 at 1:39 PM, Marques Johansson <marques+nginx at linode.com
> wrote:

> "proxy_next_upstream error" has exemptions for 402 and 403.  Should it not
> have exemptions for 429 "Too many requests" as well?
>
> I want proxied servers' 503 and 429 responses with "Retry-After" to be
> delivered to the client as the server responded.  The 429s in this case
> contain json bodies.
>
> I assume I should use proxy_pass_header to get Retry-After preserved in
> the responses, but what should I do to get 429 responses returned without
> modification (short of a feature request that proxy_next_upstream be
> modified)?
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20161019/6e2dc314/attachment.html>