Perhaps this can help:

http://stackoverflow.com/questions/12022429/http-status-code-for-overloaded-server

Another option is a *429 - Too Many Requests* response.

Defined in RFC6585 - http://tools.ietf.org/html/rfc6585#section-4

The spec does not define how the origin server identifies the user, nor how
it counts requests.

For example, an origin server that is limiting request rates can do so
based upon counts of requests on a per-resource basis, across the entire
server, or even among a set of servers.

Likewise, it might identify the user by its authentication credentials, or
a stateful cookie.

Also see the Retry-After header in the response.

Kind regards,
Oscar


On Tue, Sep 27, 2016 at 10:59 AM, itpp2012 <nginx-forum@forum.nginx.org>
wrote:

> General rule of thumb is set it as low as possible, as soon as 503's are
> getting your users upset or resources are getting blocked, then double the
> values, keep an eye on the logs, double it one more time when required,
> done.
>
> Posted at Nginx Forum: https://forum.nginx.org/read.
> php?2,269862,269866#msg-269866
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>



--
Oscar Fernandez Sierra
oscaretu@gmail.com
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx