HTTPRetryConfig
Configuration for how HTTPClient should handle retries.Parameters
The max amount of retry attempts for a request.
This is ignored when handling capacity throttling.
The max amount of seconds to wait for a request before raising the original exception. This works by keeping track of the total seconds that has been waited for the request regardless of number of attempts. If
None this is ignored.Whether or not the client should handle rate limit errors and wait the received
Retry-After before automatically retrying the request.This option is only for throttling errors with a Retry-After value.
The max amount of seconds the client should handle. If a throttled error with a higher Retry-After than this value is received, then the original HTTPException is raised instead.Only matters when
handle_rate_limits is True.Whether other requests to a rate limited endpoint should wait for the rate limit to disappear before requesting.Only matters when
handle_rate_limits is True.Whether or not the client should automatically handle capacity throttling.
Example
Route
Represents an HTTP route for making requests to Epic Games services.This class is typically used internally by the library. Most users won’t need to interact with it directly.
Example
Related
- Client - Client accepts
http_retry_configparameter - Exceptions - HTTPException can be raised during requests