3 Pf;@sddlmZddlZddlZddlmZddlmZddlZddl Z ddl m Z m Z m Z mZmZmZddlmZejeZedd d d d d gZGdddeZede_dS))absolute_importN) namedtuple) takewhile)ConnectTimeoutError MaxRetryError ProtocolErrorReadTimeoutError ResponseError InvalidHeader)sixRequestHistorymethodurlerrorstatusredirect_locationc @seZdZdZeddddddgZedgZed d d gZd Zd ddddeddddddef ddZ ddZ e d2ddZ ddZ ddZddZd3ddZdd Zd4d!d"Zd#d$Zd%d&Zd'd(Zd5d*d+Zd,d-Zd6d.d/Zd0d1ZdS)7Retrya2 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:: retries = Retry(connect=5, read=2, redirect=5) http = PoolManager(retries=retries) response = http.request('GET', 'http://example.com/') Or per-request (which overrides the default for the pool):: response = http.request('GET', 'http://example.com/', retries=Retry(10)) Retries can be disabled by passing ``False``:: response = http.request('GET', 'http://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. It's a good idea to set this to some sensibly-high value to account for unexpected edge cases and avoid infinite retry loops. 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 iterable method_whitelist: 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_METHOD_WHITELIST`. Set to a ``False`` value to retry on any verb. :param iterable 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 ``method_whitelist`` 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 total retries} - 1)) seconds. If the backoff_factor is 0.1, then :func:`.sleep` will sleep for [0.0s, 0.2s, 0.4s, ...] between retries. It will never be longer than :attr:`Retry.BACKOFF_MAX`. By default, backoff is disabled (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 iterable 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 :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. ZHEADZGETZPUTZDELETEZOPTIONSZTRACEZ Authorizationiiix NrTcCsv||_||_||_||_|dks(|dkr0d}d} ||_|p>t|_||_||_| |_ | |_ | pbt |_ | |_ | |_dS)NFr)totalconnectreadrredirectsetstatus_forcelistmethod_whitelistbackoff_factorraise_on_redirectraise_on_statustuplehistoryrespect_retry_after_headerremove_headers_on_redirect)selfrrrrrrrrrrr!r"r#r%/usr/lib/python3.6/retry.py__init__s   zRetry.__init__cKsPt|j|j|j|j|j|j|j|j|j |j |j |j d }|j |t|f|S)N) rrrrrrrrrrr!r#)dictrrrrrrrrrrr!r#updatetype)r$kwZparamsr%r%r&news  z Retry.newcCsR|dkr|dk r|n|j}t|tr(|St|o2d}|||d}tjd|||S)z4 Backwards-compatibility for the old retries format.N)rz!Converted retries value: %r -> %r)DEFAULT isinstancerboollogdebug)clsZretriesrdefaultZ new_retriesr%r%r&from_ints   zRetry.from_intcCsFtttddt|j}|dkr(dS|jd|d}t|j|S)zJ Formula for computing the current backoff :rtype: float cSs |jdkS)N)r)xr%r%r&sz(Retry.get_backoff_time..rr)lenlistrreversedr!rmin BACKOFF_MAX)r$Zconsecutive_errors_lenZ backoff_valuer%r%r&get_backoff_times  zRetry.get_backoff_timecCs\tjd|rt|}n6tjj|}|dkr6td|tj|}|tj}|dkrXd}|S)Nz^\s*[0-9]+\s*$zInvalid Retry-After header: %sr) rematchintemailZutilsZ parsedater timeZmktime)r$ retry_afterZsecondsZretry_date_tupleZ retry_dater%r%r&parse_retry_afters      zRetry.parse_retry_aftercCs |jd}|dkrdS|j|S)z* Get the value of Retry-After in seconds. z Retry-AfterN)Z getheaderrD)r$responserCr%r%r&get_retry_afters zRetry.get_retry_aftercCs |j|}|rtj|dSdS)NTF)rFrBsleep)r$rErCr%r%r&sleep_for_retrys   zRetry.sleep_for_retrycCs"|j}|dkrdStj|dS)Nr)r=rBrG)r$Zbackoffr%r%r&_sleep_backoffszRetry._sleep_backoffcCs"|r|j|}|rdS|jdS)aC 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)rHrI)r$rEZsleptr%r%r&rG s  z Retry.sleepcCs t|tS)z{ Errors when we're fairly sure that the server did not receive the request, so it should be safe to retry. )r.r)r$errr%r%r&_is_connection_errorszRetry._is_connection_errorcCst|ttfS)z Errors that occur after the request has been started, so we should assume that the server began processing it. )r.r r)r$rJr%r%r&_is_read_error!szRetry._is_read_errorcCs|jr|j|jkrdSdS)z| Checks if a given HTTP method should be retried upon, depending if it is included on the method whitelist. FT)rupper)r$rr%r%r&_is_method_retryable'szRetry._is_method_retryableFcCs<|j|sdS|jr"||jkr"dS|jo:|jo:|o:||jkS)ax Is this method/status code retryable? (Based on whitelists 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)rNrrr"RETRY_AFTER_STATUS_CODES)r$r status_codeZhas_retry_afterr%r%r&is_retry0s   zRetry.is_retrycCs:|j|j|j|j|jf}ttd|}|s.dSt|dkS)z Are we out of retries? NFr)rrrrrr9filterr;)r$Z retry_countsr%r%r& is_exhausted@s zRetry.is_exhaustedcCs|jdkr |r tjt||||j}|dk r6|d8}|j}|j} |j} |j} d} d} d}|r|j|r|dkrtjt|||n|dk r|d8}n|r|j |r| dks|j | rtjt|||n| dk r| d8} nn|o|j r| dk r| d8} d} |j }|j} n exceptionsrrrr r r Zpackagesr Z getLoggerrYr0r objectrr-r%r%r%r&s