Retry-After
An HTTP response header that a server uses to explicitly tell the client how long it should wait before retrying. The value may be expressed either as a number of seconds or as an HTTP date.
Core Facts
Timeline (last 90 days)
对于 HTTP 429，应检查 Retry-After 头，若存在则用其值替代计算出的退避延迟。
Retry-After is an HTTP response header that the server uses to explicitly tell the client how long it should wait before retrying, and the unit can be seconds or an HTTP date; clients should prioritize obeying Retry-After, and only fall back to exponential backoff when that header is missing.
The retry loop in the code attempts at most 4 times, with exponential backoff starting at 500 milliseconds, and it prioritizes obeying the Retry-After response header when the service provides one.
Some APIs explicitly inform the client how many seconds to wait via the Retry-After response header in a 429 response, which is more precise than blind backoff.
Retry-After is a standard HTTP response header through which the server informs the client, when returning a 429 or 503, how many seconds to wait before retrying.
v1.6.0 fixed the retry logic so the client respects Retry-After values exceeding 60 seconds, which previously would trigger premature retries due to an upper limit.
For invalid Retry-After values, the SDK now ignores them directly and validates maxRetries.
Some APIs include a Retry-After response header when returning 429 (Too Many Requests) to tell the client how long to wait, and that value should be used as the authoritative wait time.
The Retry-After header in an HTTP 429 response is used by the server to inform the client of the number of seconds to wait, and reading this value takes priority over calculating it independently.
All Facts (9)
The Retry-After header in an HTTP 429 response is used by the server to inform the client of the number of seconds to wait, and reading this value takes priority over calculating it independently.
65%Unverified对于 HTTP 429，应检查 Retry-After 头，若存在则用其值替代计算出的退避延迟。
50%UnverifiedThe retry loop in the code attempts at most 4 times, with exponential backoff starting at 500 milliseconds, and it prioritizes obeying the Retry-After response header when the service provides one.
50%UnverifiedRetry-After is an HTTP response header that the server uses to explicitly tell the client how long it should wait before retrying, and the unit can be seconds or an HTTP date; clients should prioritize obeying Retry-After, and only fall back to exponential backoff when that header is missing.
50%UnverifiedSome APIs explicitly inform the client how many seconds to wait via the Retry-After response header in a 429 response, which is more precise than blind backoff.
50%Unverifiedv1.6.0 fixed the retry logic so the client respects Retry-After values exceeding 60 seconds, which previously would trigger premature retries due to an upper limit.
50%UnverifiedRetry-After is a standard HTTP response header through which the server informs the client, when returning a 429 or 503, how many seconds to wait before retrying.
50%UnverifiedFor invalid Retry-After values, the SDK now ignores them directly and validates maxRetries.
50%UnverifiedSome APIs include a Retry-After response header when returning 429 (Too Many Requests) to tell the client how long to wait, and that value should be used as the authoritative wait time.
50%