Retry-After
The response header that tells a client how long to wait, in seconds or as a date, before trying again.
In more detail
It appears on 429 Too Many Requests and 503 Service Unavailable. Clients should respect it and still add jitter, because many callers receive the same advice.
Example
Retry-After: 30Related terms
- 429 Too Many Requests — The HTTP status meaning the caller has sent too many requests in a given time and should slow down.
- backoff — Waiting longer and longer between successive retries, often doubling the delay each time, so a struggling service has room to recover.
- rate limiting — Capping how many requests a client may make in a period of time, and rejecting or delaying the rest.
- exponential backoff — Waiting progressively longer between retries, for example 1, 2, then 4 seconds, so a struggling service gets room to recover.
- jitter — A random amount added to or taken from a retry delay so that many clients do not all retry at the same moment.
- HTTP status code — The three-digit number at the start of a response, such as 200 or 404, that says how the server handled the request.
- RateLimit header fields — Response headers that tell a client its rate-limit budget: the limit, how much remains and when it resets.
Taught in
- When The Call Fails — AI Engineering: LLM Apps, RAG & Agents
- Error Handling And Safe Retries — Modern API Architecture: REST, GraphQL & gRPC
- Rate Limiting Strategies — Modern API Architecture: REST, GraphQL & gRPC
- Built-in Rate Limiting Middleware — Modern .NET Core, C# & Enterprise Microservices
- Traffic Management: Sliding Window Rate Limiting — Production Full-Stack Engineering
- Rate Limiting And Resource Consumption — Application Security & Threat Modeling for Engineers
References
- RFC 9110: HTTP Semantics, section 10.2.3 Retry-After
- MDN: Retry-After
- RFC 9110: Retry-After
- RFC 9110: Retry-After