rate limiting client Shipped
What this lens looks for
Clients must respect server rate limits and handle 429 Too Many Requests responses gracefully: on a 429 the client must honor the Retry-After header (whether expressed as a delay in seconds or as an HTTP-date) before retrying; when no Retry-After is present, fall back to exponential backoff rather than immediate retry; clients should proactively track the RateLimit-Remaining header and slow down before they hit a 429 rather than waiting to be rejected; outbound requests should be queued and batched to stay at the allowed rate instead of a fire-and-retry loop that hammers the server.
What its verifier checks
A 429 response causes the client to wait for the duration given by Retry-After (parsing both the seconds and HTTP-date forms) before retrying; when Retry-After is absent, retries use exponential backoff and never a tight immediate-retry loop; the client reads RateLimit-Remaining and throttles ahead of the limit where the header is available; requests are queued/batched to the allowed rate rather than fired and blindly retried.