📁 File Manager Pro
v10.0.3 | PHP: 8.1.34
Server: LiteSpeed
2026-06-29 19:02:31
📂
/ (Root)
/
opt
/
hc_python
/
lib
/
python3.12
/
site-packages
/
urllib3
/
__pycache__
📍 /opt/hc_python/lib/python3.12/site-packages/urllib3/__pycache__
🔄 Refresh
✏️
Editing: _request_methods.cpython-312.pyc
Read Only
� 8��g�& � � � d dl mZ d dlZd dlZd dlmZ ddlmZ ddl m Z ddl m Z m Z ddlmZ d gZej" ej$ eeej" eef f ej, eej" eef f f Z G d � d � Zy) � )� annotationsN)� urlencode� )� _TYPE_BODY)�HTTPHeaderDict)� _TYPE_FIELDS�encode_multipart_formdata)�BaseHTTPResponse�RequestMethodsc �� � e Zd ZdZh d�Zd d d�Z d d d�Z d dd�Z d dd�Z d dd�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 �G/opt/hc_python/lib/python3.12/site-packages/urllib3/_request_methods.py�__init__zRequestMethods.__init__3 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.urlopen6 s � � "� ,� � r c � � |j � }|� |� t d� �|�o|� | j }dt t j |j � � vrt |� }d|d< t j |dd�� j d� }|�||d < || j v r | j ||f||d �|��S | j ||f||d �|��S ) ay 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`. :param method: HTTP request method (such as GET, POST, PUT, etc.) :param url: The URL to perform the request on. :param body: Data to send in the request body, either :class:`str`, :class:`bytes`, an iterable of :class:`str`/:class:`bytes`, or a file-like object. :param fields: Data to encode and send in the URL or request body, depending on ``method``. :param headers: Dictionary of custom headers to send, such as User-Agent, If-None-Match, etc. If None, pool headers are used. If provided, these headers completely replace any pool-specific headers. :param json: Data to encode and send as JSON with UTF-encoded in the request body. The ``"Content-Type"`` header will be set to ``"application/json"`` unless specified otherwise. zUrequest got values for both 'body' and 'json' parameters which are mutually exclusivez content-typezapplication/json� Content-Type)�,�:F)� separators� ensure_asciizutf-8r )�fieldsr )�upper� TypeErrorr �map�str�lower�keysr �_json�dumps�encode�_encode_url_methods�request_encode_url�request_encode_body)r r r r r' r �json� urlopen_kws r �requestzRequestMethods.requestE s � �V � � � �� � �� 0��g�� � � ��� �,�,��"�c�#�)�)�W�\�\�^�&D�D�(��1��*<���'��;�;�t� ��O�V�V���D� � �!%�J�v� � �T�-�-� -�*�4�*�*���� � � � � � � ,�4�+�+����$*�G��?I�� r c � � |� | j }d|i}|j |� |r|dt |� z z } | j ||fi |��S )a} Make a request using :meth:`urlopen` with the ``fields`` encoded in the url. This is useful for request methods like GET, HEAD, DELETE, etc. :param method: HTTP request method (such as GET, POST, PUT, etc.) :param url: The URL to perform the request on. :param fields: Data to encode and send in the URL. :param headers: Dictionary of custom headers to send, such as User-Agent, If-None-Match, etc. If None, pool headers are used. If provided, these headers completely replace any pool-specific headers. r �?)r �updater r )r r r r' r r5 �extra_kws r r2 z!RequestMethods.request_encode_url� sW � �4 �?��l�l�G�+4�g�*>����� �#� � �3��6�*�*� *�C��t�|�|�F�C�4�8�4�4r c � � |� | j }dt |� i}|rId|v r t d� �|rt ||�� \ } } n t |� d} } | |d< |d j d| � |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. :param method: HTTP request method (such as GET, POST, PUT, etc.) :param url: The URL to perform the request on. :param fields: Data to encode and send in the request body. :param headers: Dictionary of custom headers to send, such as User-Agent, If-None-Match, etc. If None, pool headers are used. If provided, these headers completely replace any pool-specific headers. :param encode_multipart: If True, encode the ``fields`` using the multipart/form-data MIME format. :param multipart_boundary: If not specified, then a random boundary will be generated using :func:`urllib3.filepost.choose_boundary`. r r zFrequest got values for both 'fields' and 'body', can only specify one.)�boundaryz!application/x-www-form-urlencodedr" )r r r) r r � setdefaultr9 r ) r r r r' r r r r5 r: r � content_types r r3 z"RequestMethods.request_encode_body� s� � �F �?��l�l�G�+4�n�W�6M�*N�� ���#� �\�� � �%>��%7�&�"��l� �f�%�7� #�� $�H�V� � �Y� � *� *�>�<� H���� �#��t�|�|�F�C�4�8�4�4r r )r � typing.Mapping[str, str] | None�return�None)NNTN)r r+ r r+ r �_TYPE_BODY | Noner r? r �boolr � str | Noner � typing.Anyr@ r )NNNN)r r+ r r+ r rB r' �_TYPE_FIELDS | Noner r? r4 ztyping.Any | Noner5 rE r@ r )NN) r r+ r r+ r' z _TYPE_ENCODE_URL_FIELDS | Noner r? r5 r+ r@ r )r r+ r r+ r' rF r r? r rC r rD r5 r+ r@ r ) �__name__� __module__� __qualname__�__doc__r1 r r r6 r2 r3 � r r r r s� � ��8 ?��%� #'�37�!%�)-� �� � � � � � 1� � � � '� � � � � �& #'�&*�37�"&�L��L� �L� � L� $� L� 1� L� �L� !�L� �L�d 26�37� #5��#5� �#5� /� #5� 1� #5� � #5� �#5�R '+�37�!%�)-�^5��^5� �^5� $� ^5� 1� ^5� � ^5� '�^5� �^5� �^5r )� __future__r r4 r. �typing� urllib.parser �_base_connectionr � _collectionsr �filepostr r �responser �__all__�Union�Sequence�tupler+ �bytes�Mapping�_TYPE_ENCODE_URL_FIELDSr rK r r �<module>rZ s� �� "� � � "� (� (� =� &� � �� �,�,� �O�O�E�#�v�|�|�C��J� 7�7�8�9� �N�N�3�� � �S�%�Z�0�0�1�3�� � B5� B5r
💾 Save Changes
❌ Cancel