U
fH @ s d dl mZ d dlZd dlZd dlZd dlZd dlZd dlZd dlm Z d dl
m Z ddl m
Z
mZmZmZmZmZmZ ddlmZ ejrd d lmZ dd
lmZ dd lm Z e e Z G d d
d
ej Z!G dd dZ"e"de"_#dS ) ) annotationsN) takewhile)
TracebackType )ConnectTimeoutError
InvalidHeader
MaxRetryError
ProtocolError
ProxyErrorReadTimeoutError
ResponseError )reraise)Self)ConnectionPool)BaseHTTPResponsec @ s6 e Zd ZU ded< ded< ded< ded< ded< d S )
RequestHistory
str | NonemethodurlException | Noneerror
int | Nonestatusredirect_locationN)__name__
__module__ __qualname____annotations__ r r C/opt/alt/python38/lib/python3.8/site-packages/urllib3/util/retry.pyr ! s
r c @ s e Zd ZU dZeddddddgZedd d
gZed d d
gZdZde d< ddddddeddeddddedfddddddddddddd dd dd d d d!Z
d"d#d$d%d&Z e dWd'dd'd d(d)d*Z
dd+d,d-Zd.dd/d0d1Zd2d3d4d5d6Zd2dd4d7d8Zd d+d9d:ZdXd;d d4ddd?d@dAZd>dd?dBdCZd.ddDdEdFZdYd.dHdddIdJdKZdd+dLdMZdZdNdNd;dOdPdQd#dRdSdTZd.d+dUdVZdS )[Retrya Retry configuration.
Each retry attempt will create a new Retry object with updated values, so
they can be safely reused.
Retries can be defined as a default for a pool:
.. code-block:: python
retries = Retry(connect=5, read=2, redirect=5)
http = PoolManager(retries=retries)
response = http.request("GET", "https://example.com/")
Or per-request (which overrides the default for the pool):
.. code-block:: python
response = http.request("GET", "https://example.com/", retries=Retry(10))
Retries can be disabled by passing ``False``:
.. code-block:: python
response = http.request("GET", "https://example.com/", retries=False)
Errors will be wrapped in :class:`~urllib3.exceptions.MaxRetryError` unless
retries are disabled, in which case the causing exception will be raised.
:param int total:
Total number of retries to allow. Takes precedence over other counts.
Set to ``None`` to remove this constraint and fall back on other
counts.
Set to ``0`` to fail on the first retry.
Set to ``False`` to disable and imply ``raise_on_redirect=False``.
:param int connect:
How many connection-related errors to retry on.
These are errors raised before the request is sent to the remote server,
which we assume has not triggered the server to process the request.
Set to ``0`` to fail on the first retry of this type.
:param int read:
How many times to retry on read errors.
These errors are raised after the request was sent to the server, so the
request may have side-effects.
Set to ``0`` to fail on the first retry of this type.
:param int redirect:
How many redirects to perform. Limit this to avoid infinite redirect
loops.
A redirect is a HTTP response with a status code 301, 302, 303, 307 or
308.
Set to ``0`` to fail on the first retry of this type.
Set to ``False`` to disable and imply ``raise_on_redirect=False``.
:param int status:
How many times to retry on bad status codes.
These are retries made on responses, where status code matches
``status_forcelist``.
Set to ``0`` to fail on the first retry of this type.
:param int other:
How many times to retry on other errors.
Other errors are errors that are not connect, read, redirect or status errors.
These errors might be raised after the request was sent to the server, so the
request might have side-effects.
Set to ``0`` to fail on the first retry of this type.
If ``total`` is not set, it's a good idea to set this to 0 to account
for unexpected edge cases and avoid infinite retry loops.
:param Collection allowed_methods:
Set of uppercased HTTP method verbs that we should retry on.
By default, we only retry on methods which are considered to be
idempotent (multiple requests with the same parameters end with the
same state). See :attr:`Retry.DEFAULT_ALLOWED_METHODS`.
Set to a ``None`` value to retry on any verb.
:param Collection status_forcelist:
A set of integer HTTP status codes that we should force a retry on.
A retry is initiated if the request method is in ``allowed_methods``
and the response status code is in ``status_forcelist``.
By default, this is disabled with ``None``.
:param float backoff_factor:
A backoff factor to apply between attempts after the second try
(most errors are resolved immediately by a second try without a
delay). urllib3 will sleep for::
{backoff factor} * (2 ** ({number of previous retries}))
seconds. If `backoff_jitter` is non-zero, this sleep is extended by::
random.uniform(0, {backoff jitter})
seconds. For example, if the backoff_factor is 0.1, then :func:`Retry.sleep` will
sleep for [0.0s, 0.2s, 0.4s, 0.8s, ...] between retries. No backoff will ever
be longer than `backoff_max`.
By default, backoff is disabled (factor set to 0).
:param bool raise_on_redirect: Whether, if the number of redirects is
exhausted, to raise a MaxRetryError, or to return a response with a
response code in the 3xx range.
:param bool raise_on_status: Similar meaning to ``raise_on_redirect``:
whether we should raise an exception, or return a response,
if status falls in ``status_forcelist`` range and retries have
been exhausted.
:param tuple history: The history of the request encountered during
each call to :meth:`~Retry.increment`. The list is in the order
the requests occurred. Each list item is of class :class:`RequestHistory`.
:param bool respect_retry_after_header:
Whether to respect Retry-After header on status codes defined as
:attr:`Retry.RETRY_AFTER_STATUS_CODES` or not.
:param Collection remove_headers_on_redirect:
Sequence of headers to remove from the request when a response
indicating a redirect is returned before firing off the redirected
request.
HEADGETPUTDELETEOPTIONSTRACEi i i Cookie
AuthorizationzProxy-Authorizationx ztyping.ClassVar[Retry]DEFAULT
Nr T zbool | int | Noner z typing.Collection[str] | Nonez typing.Collection[int] | Nonefloatboolz!tuple[RequestHistory, ...] | Noneztyping.Collection[str]None)totalconnectreadredirectr otherallowed_methodsstatus_forcelistbackoff_factor backoff_maxraise_on_redirectraise_on_statushistoryrespect_retry_after_headerremove_headers_on_redirectbackoff_jitterreturnc C s || _ || _|| _|| _|| _|dks.|dkr6d}d} || _|pDt | _|| _| | _ |
| _
| | _ | | _ |
pld| _
|| _tdd |D | _|| _d S )NFr r c s s | ]}| V qd S N)lower).0hr r r s z!Retry.__init__..)r1 r2 r3 r r5 r4 setr7 r6 r8 r9 r: r; r< r= frozensetr> r? )selfr1 r2 r3 r4 r r5 r6 r7 r8 r9 r: r; r< r= r> r? r r r __init__ s*
zRetry.__init__z
typing.Anyr )kwr@ c K s` t | j| j| j| j| j| j| j| j| j | j
| j | j | j
| j| j| jd}|| t| f |S )N)r1 r2 r3 r4 r r5 r6 r7 r8 r9 r: r; r< r> r= r? )dictr1 r2 r3 r4 r r5 r6 r7 r8 r9 r: r; r< r> r= r? updatetype)rH rJ paramsr r r new s(
z Retry.newzRetry | bool | int | None)retriesr4 defaultr@ c C sR |dkr|dk r|n| j }t|tr(|S t|o2d}| ||d}td|| |S )z3Backwards-compatibility for the old retries format.N)r4 z!Converted retries value: %r -> %r)r+
isinstancer! r/ logdebug)clsrP r4 rQ new_retriesr r r from_int s
zRetry.from_int)r@ c C sl t ttdd t| j}|dkr(dS | jd|d }| jdkrV|t | j 7 }tt dt
| j |S )zIFormula for computing the current backoff
:rtype: float
c S s
| j d kS rA )r )xr r r ) z(Retry.get_backoff_time..r
r r r- ) lenlistr reversedr< r8 r? randomr. maxminr9 )rH consecutive_errors_len
backoff_valuer r r get_backoff_time! s
zRetry.get_backoff_timestr) retry_afterr@ c C s^ t d|rt|}n:tj|}|d kr8td| tj|}|t }t |d}|S )Nz^\s*[0-9]+\s*$z Invalid Retry-After header: r )
rematchintemailutils parsedate_tzr mktime_tztimer_ )rH re secondsretry_date_tuple
retry_dater r r parse_retry_after4 s
zRetry.parse_retry_afterr z float | None)responser@ c C s" |j d}|dkrdS | |S )z(Get the value of Retry-After in seconds.z Retry-AfterN)headersgetrq rH rr re r r r get_retry_afterE s zRetry.get_retry_afterc C s | |}|r t| dS dS )NTF)rv rm sleepru r r r sleep_for_retryO s
zRetry.sleep_for_retryc C s" | }|dkrd S t| d S )Nr )rc rm rw )rH backoffr r r _sleep_backoffW s zRetry._sleep_backoffzBaseHTTPResponse | Nonec C s( | j r |r | |}|r dS | dS )aB Sleep between retry attempts.
This method will respect a server's ``Retry-After`` response header
and sleep the duration of the time requested. If that is not present, it
will use an exponential backoff. By default, the backoff factor is 0 and
this method will return immediately.
N)r= rx rz )rH rr sleptr r r rw ] s
z Retry.sleep Exception)errr@ c C s t |tr|j}t |tS )zzErrors when we're fairly sure that the server did not receive the
request, so it should be safe to retry.
)rR r
original_errorr rH r} r r r _is_connection_errorm s
zRetry._is_connection_errorc C s t |ttfS )zErrors that occur after the request has been started, so we should
assume that the server began processing it.
)rR r r r r r r _is_read_erroru s zRetry._is_read_error)r r@ c C s | j r| | j krdS dS )zyChecks if a given HTTP method should be retried upon, depending if
it is included in the allowed_methods
FT)r6 upper)rH r r r r _is_method_retryable{ s zRetry._is_method_retryableFrh )r status_codehas_retry_afterr@ c C s@ | |sdS | jr"|| jkr"dS t| jo<| jo<|o<|| jkS )aw Is this method/status code retryable? (Based on allowlists and control
variables such as the number of total retries to allow, whether to
respect the Retry-After header, whether this header is present, and
whether the returned status code is on the list of status codes to
be retried upon on the presence of the aforementioned header)
FT)r r7 r/ r1 r= RETRY_AFTER_STATUS_CODES)rH r r r r r r is_retry s
zRetry.is_retryc C s: dd | j | j| j| j| j| jfD }|s.dS t|dk S )zAre we out of retries?c S s g | ] }|r|qS r r )rC rX r r r
s z&Retry.is_exhausted..Fr )r1 r2 r3 r4 r r5 r` )rH retry_countsr r r is_exhausted s zRetry.is_exhaustedr r zConnectionPool | NonezTracebackType | None)r r rr r _pool _stacktracer@ c C s | j dkr |r tt|||| j }|dk r4|d8 }| j}| j} | j}
| j} | j} d}
d}d}|r| |r|dkrtt|||n|dk r|d8 }n|r| |r| dks|dks|
|stt|||n| dk r| d8 } n|r| dk r| d8 } n||r:| r:|
dk r |
d8 }
d}
| }|r2|}|j}n s* $
o