Available on crate features
async or sync only.Expand description
Retry policy honoring Retry-After.
RetryPolicy decides when and how long to wait between attempts.
Error::is_retryable decides
whether a given error is worth retrying. The retry loop itself lives on
Client::execute_with_retry and combines the two.
Defaults are conservative: 3 attempts, exponential backoff from 500 ms to
30 s, full jitter, Retry-After honored. Replace via
ClientBuilder::retry.
Structs§
- Retry
Policy - Retry policy applied to outbound requests.
Enums§
- Jitter
- Jitter strategy applied to the computed backoff.