|
Server : Apache System : Linux cvar2.toservers.com 3.10.0-962.3.2.lve1.5.73.el7.x86_64 #1 SMP Wed Aug 24 21:31:23 UTC 2022 x86_64 User : njnconst ( 1116) PHP Version : 8.4.18 Disable Function : NONE Directory : /opt/alt/python33/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3/ |
Upload File : |
�
�2{Yc @ sk y d d l m Z Wn! e k
r7 d d l m Z n Xd d l m Z d g Z d e f d � � YZ d S( i����( t urlencodei ( t encode_multipart_formdatat RequestMethodsc B sw e Z d Z e d d d d g � Z d
d � Z d
d
e d
d � Z d
d
d � Z d
d � Z
d
d
e d
d � Z RS( s�
Convenience mixin for classes who implement a :meth:`urlopen` method, such
as :class:`~urllib3.connectionpool.HTTPConnectionPool` and
:class:`~urllib3.poolmanager.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.
t DELETEt GETt HEADt OPTIONSc C s | p i | _ d S( N( t headers( t selfR ( ( s^ /opt/alt/python33/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3/request.pyt __init__1 s c K s t d � � d S( NsM Classes extending RequestMethods must implement their own ``urlopen`` method.( t NotImplemented( R t methodt urlt bodyR t encode_multipartt multipart_boundaryt kw( ( s^ /opt/alt/python33/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3/request.pyt urlopen4 s c K s] | j � } | | j k r: | j | | d | d | | �S| j | | d | d | | �Sd S( s�
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`.
t fieldsR N( t uppert _encode_url_methodst request_encode_urlt request_encode_body( R R R R R t
urlopen_kw( ( s^ /opt/alt/python33/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3/request.pyt request: s c K s0 | r | d t | � 7} n | j | | | � S( s�
Make a request using :meth:`urlopen` with the ``fields`` encoded in
the url. This is useful for request methods like GET, HEAD, DELETE, etc.
t ?( R R ( R R R R R ( ( s^ /opt/alt/python33/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3/request.pyR P s c K s� | r' t | p i d | �\ } } n t | p3 i � d } } | d k rX | j } n i | d 6}
|
j | � | j | | d | d |
| �S( s�
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
:meth:`urllib3.filepost.encode_multipart_formdata` is used to encode the
payload with the appropriate content type. Otherwise
:meth:`urllib.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 mimick 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.
t boundarys! application/x-www-form-urlencodeds Content-TypeR
R N( R R t NoneR t updateR ( R R R R R R R R R
t content_typet headers_( ( s^ /opt/alt/python33/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3/request.pyR Y s &
N( t __name__t
__module__t __doc__t setR R R t TrueR R R R ( ( ( s^ /opt/alt/python33/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3/request.pyR s N( t urllib.parseR t ImportErrort urllibt filepostR t __all__t objectR ( ( ( s^ /opt/alt/python33/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3/request.pyt <module> s