| Server IP : 209.209.40.120 / Your IP : 216.73.217.112 Web Server : Microsoft-IIS/10.0 System : Windows NT NEWWWW 10.0 build 17763 (Windows Server 2019) i586 User : NEWWWW$ ( 0) PHP Version : 8.3.30 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : C:/Python312/Lib/site-packages/pip/_vendor/urllib3/__pycache__/ |
Upload File : |
�
�k�f# � �� � d dl mZ d dlZddlmZ ddlmZ ddlmZ dgZ G d� de
� Z ej s7 G d � d
ej e j � Zeej e _ yy) � )�absolute_importN� )�encode_multipart_formdata)�six)� urlencode�RequestMethodsc �P � e Zd ZdZh d�Zd d�Z d
d�Zd d�Zd d�Z d
d�Z y) r a�
Convenience mixin for classes who implement a :meth:`urlopen` method, such
as :class:`urllib3.HTTPConnectionPool` and
:class:`urllib3.PoolManager`.
Provides behavior for making common types of HTTP request methods and
decides which type of request field encoding to use.
Specifically,
:meth:`.request_encode_url` is for sending requests whose fields are
encoded in the URL (such as GET, HEAD, DELETE).
:meth:`.request_encode_body` is for sending requests whose fields are
encoded in the *body* of the request using multipart or www-form-urlencoded
(such as for POST, PUT, PATCH).
:meth:`.request` is for making any kind of request, it will look up the
appropriate encoding format and use one of the above two methods to make
the request.
Initializer parameters:
:param headers:
Headers to include with all requests, unless other headers are given
explicitly.
> �GET�HEAD�DELETE�OPTIONSNc � � |xs i | _ y �N)�headers)�selfr s �=C:\Python312\Lib\site-packages\pip/_vendor/urllib3/request.py�__init__zRequestMethods.__init__+ s
� � �}�"�� � c � � t d� �)NzMClasses extending RequestMethods must implement their own ``urlopen`` method.)�NotImplementedError)r �method�url�bodyr �encode_multipart�multipart_boundary�kws r �urlopenzRequestMethods.urlopen. s � � "�
,�
�
r c � � |j � }||d< || j v r | j ||f||d�|��S | j ||f||d�|��S )a�
Make a request using :meth:`urlopen` with the appropriate encoding of
``fields`` based on the ``method`` used.
This is a convenience method that requires the least amount of manual
effort. It can be used in most situations, while still having the
option to drop down to more specific methods when necessary, such as
:meth:`request_encode_url`, :meth:`request_encode_body`,
or even the lowest level :meth:`urlopen`.
� request_url)�fieldsr )�upper�_encode_url_methods�request_encode_url�request_encode_body)r r r r r �
urlopen_kws r �requestzRequestMethods.request= s� � � � � � ��$'�
�=�!� �T�-�-� -�*�4�*�*����$*�G��?I��
� ,�4�+�+����$*�G��?I��
r c � � |� | j }d|i}|j |� |r|dt |� z z
} | j ||fi |��S )z�
Make a request using :meth:`urlopen` with the ``fields`` encoded in
the url. This is useful for request methods like GET, HEAD, DELETE, etc.
r �?)r �updater r )r r r r r r% �extra_kws r r# z!RequestMethods.request_encode_urlU sW � �
�?��l�l�G� �w�'�����
�#� � �3��6�*�*� *�C��t�|�|�F�C�4�8�4�4r c � � |� | j }di i}|r;d|v r t d� �|rt ||�� \ } }
n
t |� d}
} | |d< d|
i|d< |d j |� |j |� | j
||fi |��S )a�
Make a request using :meth:`urlopen` with the ``fields`` encoded in
the body. This is useful for request methods like POST, PUT, PATCH, etc.
When ``encode_multipart=True`` (default), then
:func:`urllib3.encode_multipart_formdata` is used to encode
the payload with the appropriate content type. Otherwise
:func:`urllib.parse.urlencode` is used with the
'application/x-www-form-urlencoded' content type.
Multipart encoding must be used when posting files, and it's reasonably
safe to use it in other times too. However, it may break request
signing, such as with OAuth.
Supports an optional ``fields`` parameter of key/value strings AND
key/filetuple. A filetuple is a (filename, data, MIME type) tuple where
the MIME type is optional. For example::
fields = {
'foo': 'bar',
'fakefile': ('foofile.txt', 'contents of foofile'),
'realfile': ('barfile.txt', open('realfile').read()),
'typedfile': ('bazfile.bin', open('bazfile').read(),
'image/jpeg'),
'nonamefile': 'contents of nonamefile field',
}
When uploading a file, providing a filename (the first parameter of the
tuple) is optional but recommended to best mimic behavior of browsers.
Note that if ``headers`` are supplied, the 'Content-Type' header will
be overwritten because it depends on the dynamic random boundary string
which is used to compose the body of the request. The random boundary
string can be explicitly set with the ``multipart_boundary`` parameter.
r r zFrequest got values for both 'fields' and 'body', can only specify one.)�boundaryz!application/x-www-form-urlencodedz Content-Type)r � TypeErrorr r r) r ) r r r r r r r r% r* r � content_types r r$ z"RequestMethods.request_encode_bodye s� � �Z �?��l�l�G� �r�?�� ���#� �\�� � �%>��%7�&�"��l�
�f�%�7� #��
$�H�V� �#1�<�"@�H�Y� ����"�"�7�+����
�#��t�|�|�F�C�4�8�4�4r r )NNTN)NN)
�__name__�
__module__� __qualname__�__doc__r" r r r& r# r$ � r r r r sE � ��8 ?��%� �� � �
� �05�( �� � �H5r c � � e Zd Zd� Zy)�
RequestModulec � � t d� �)z�
If user tries to call this module directly urllib3 v2.x style raise an error to the user
suggesting they may need urllib3 v2
z�'module' object is not callable
urllib3.request() method is not supported in this release, upgrade to urllib3 v2 to use it
see https://urllib3.readthedocs.io/en/stable/v2-migration-guide.html)r- )r �args�kwargss r �__call__zRequestModule.__call__� s � �
�W��
r N)r/ r0 r1 r9 r3 r r r5 r5 � s � �
r r5 )�
__future__r �sys�filepostr �packagesr � packages.six.moves.urllib.parser �__all__�objectr �PY2�modulesr/ � __class__r5 r3 r r �<module>rD sg �� &�
� /� � 6� �
��a5�V� a5�H �w�w� �� � �H�-�7�7� � '4�C�K�K���#� r