The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Retry-After tells an API client how long the server says it ought to wait before making a follow-up request. On a 429 Too Many Requests response, it is a useful rate-limit timing hint—but it does not guarantee that another attempt is safe, and the header may be absent.
What does Retry-After mean?
The Retry-After response header supplies a wait interval or time before a follow-up request. RFC 9110 describes it as guidance about when to make another request, not a guarantee that the request will succeed or that repeating an operation is safe. See RFC 9110, Section 10.2.3.
As an Amazon Associate I earn from qualifying purchases.
For rate limiting, the common context is HTTP 429 Too Many Requests. RFC 6585 defines 429 for a client that has sent too many requests in a given period; the response may include Retry-After to indicate how long to wait before a new request. The header is optional, not required. See RFC 6585, Section 4.
How to read its two value formats
RFC 9110 permits either an HTTP date or a delay in seconds:
#1 Best Overall
| Format | Example | How to interpret it |
|---|---|---|
| Delay in seconds | Retry-After: 120 |
Wait 120 seconds—two minutes—from receipt of the response before making the follow-up request. |
| HTTP date | Retry-After: Fri, 31 Dec 1999 23:59:59 GMT |
The value is an absolute time. Parse it as an HTTP date and wait until that time before proceeding. |
The numeric form consists of one or more decimal digits and represents a non-negative delay. A client implementing the standard should handle both forms rather than assuming the value is always a number. The date form requires interpreting an absolute time; the numeric form is relative to when the response is received. Both formats are defined in RFC 9110.
When the same header means something else
Do not interpret every Retry-After value as a rate-limit signal. Its meaning depends on the response status:
Rank #2
- Used Book in Good Condition
- 429 Too Many Requests: the server may give a wait interval before a new request. RFC 6585 does not require the field to be present.
- 503 Service Unavailable: the field indicates how long the service is expected to be unavailable.
- 3xx redirection: the field gives the minimum time to wait before issuing the redirected request.
These status-specific meanings are set out in RFC 9110; the 429 definition is in RFC 6585.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteShould a client retry when it receives Retry-After?
First decide whether the operation may safely be repeated; then use the header to decide when a permitted retry can occur. A delay does not make replaying a request safe. RFC 9110 says clients should not automatically retry a non-idempotent request unless they know its semantics are idempotent or can determine that the original request was not applied. This distinction matters for operations that can create or change something: the server may have acted even if the client received an error response.
A sound handling flow is:
- Check the response status. Distinguish 429 rate limiting from 503 unavailability or a 3xx redirect.
- Read and parse the header. Accept an HTTP date or a decimal delay in seconds.
- Check retry eligibility. Consider whether repeating the operation is safe, idempotent, or known not to have been applied.
- Wait before the follow-up request. If the response provides a valid value and a retry is appropriate, honor the indicated timing.
- Apply your client’s retry limits. Bound attempts and avoid loops. The cited RFC sections do not set a universal attempt count or a universal fallback for a missing or invalid header.
The exact fallback for an absent or unusable value, retry cap, and interaction with other backoff policies depend on the client or API implementation; the RFCs cited here do not prescribe one shared algorithm.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What a 429 does—and does not—tell you
A 429 indicates that the server considers the request rate too high, but it does not reveal a universal quota or counting scope. RFC 6585 leaves open how a server identifies a user and counts requests: the limit might apply per resource, across a server, across servers, or according to credentials or cookies. A client should not infer those details from the status code alone.
RFC 6585 also specifies that 429 responses must not be stored by a cache. That caching rule does not change the separate question of whether an application should retry a particular operation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
