tooManyRequests
4.29 Too Many Requests (RFC 8516 §3), for a client that sends requests more often than the server can or will handle: its Max-Age is retryAfter in whole seconds, rounded up so the client never comes back too early, and at most 2^32 - 1 (RFC 7252 §5.10.5); the client should not send a similar request before that (RFC 8516 §4). diagnostic becomes the diagnostic payload (RFC 7252 §5.5.2), which may say more about the overload. RFC 8516 §3 keeps 4.29 for the clients that send too often; an overload that all clients cause gets 5.03 Service Unavailable, with Max-Age as well.
Throws
when retryAfter is negative.