proxy_next_upstream exemption for 429 "too many requests"

[Marques Johansson]

I was mistaken.  I wasn't triggering 429s reliably.  They are being passed
through as expected.

I will use proxy_pass_header Retry-After to get the behavior I wanted for
503s.

Some of my server 503s may be application/json while others are text/html.

I would like to pass the json responses through while nginx returns its
own 503 response instead of server 503 html responses.

That doesn't seem to be possible with the existing proxy options.

On Wed, Oct 19, 2016 at 8:37 PM, Piotr Sikora <piotrsikora at google.com>
wrote:

> Hey Marques,
>
> > "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.
>
> Actually, after re-reading your email, I'm confused... 429 responses
> aren't matched by "proxy_next_upstream error" (with or without my
> patches), and are passed as-is to the client.
>
> Maybe you're using "proxy_intercept_errors" with custom error pages?
>
> Best regards,
> Piotr Sikora
>
> _______________________________________________
> 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/20161020/3a4a4543/attachment.html>