Available on crate features
aws-base or azure-base or gcp-base only.Expand description
Retry policies for HTTP-backed multipart uploads
Each multipart part first uses the backend’s existing bounded request retry
loop. If those retries are exhausted, a RetryPolicy can restart the
entire part operation. Restarting at this boundary rebuilds the request,
including fetching credentials and generating a new signature.
Configure a policy with PutMultipartOptions::with_retry_policy. The
policy applies independently to each part and does not change the retry
behavior of multipart initiation, completion, or abort requests.
Structs§
- Retry
Context - The failure and retry state for one operation attempt
Enums§
- Retry
Failure - A normalized HTTP failure passed to a
RetryPolicy
Traits§
- Retry
Policy - Controls whether and when a failed operation should be attempted again