[PATCH 1 of 2] HTTP: add support for "429 Too Many Requests" response (RFC6585)

[Maxim Dounin]

Hello!

On Wed, Feb 22, 2017 at 07:38:15PM -0800, Piotr Sikora via nginx-devel wrote:

> Hey,
> 
> > # HG changeset patch
> > # User Piotr Sikora <piotrsikora at google.com>
> > # Date 1476859139 25200
> > #      Tue Oct 18 23:38:59 2016 -0700
> > # Node ID 1eec5355ef1e4a8b0aecebdec84c744734c0d36e
> > # Parent  8081e1f3ab8b9ccb4e2d7f9240cbfb8e404a3c95
> > HTTP: add support for "429 Too Many Requests" response (RFC6585).
> >
> > This change adds reason phrase in status line and pretty response body
> > when "429" status code is used in "return", "limit_conn_status" and/or
> > "limit_req_status" directives.
> >
> > It also adds "http_429" parameter to "proxy_next_upstream" for retrying
> > rate-limited requests, and to "proxy_cache_use_stale" for serving stale
> > cached responses after being rate-limited.
> 
> Ping...

I certainly disagree with the second patch of the series.

The first one looks acceptable, though it might be a better idea 
to split it into two separate patches.

-- 
Maxim Dounin
http://nginx.org/