HEX

File: //usr/lib/python3/dist-packages/mercurial/hgweb/__pycache__/request.cpython-310.pyc
o

�]Lb
Y�@s�ddlmZddlmZddlmZmZmZmZddl	m
Z
Gdd�de�Zej
dd	�Gd
d�de��Zdd
d�ZGdd�de�ZGdd�de�Zdd�ZdS)�)�absolute_import�)�attr)�encoding�error�pycompat�util)�urlutilc@sjeZdZdZdd�Zdd�Zdd�Zdd	�Zd
d�Zdd
�Z	ddd�Z
dd�Zdd�Zdd�Z
dd�ZdS)�	multidictz�A dict like object that can store multiple values for a key.

    Used to store parsed request parameters.

    This is inspired by WebOb's class of the same name.
    cCs
i|_dS�N��_items��self�r�9/usr/lib/python3/dist-packages/mercurial/hgweb/request.py�__init__!�
zmultidict.__init__cCs|j|dS)z%Returns the last set value for a key.���r�r�keyrrr�__getitem__$�zmultidict.__getitem__cCs|g|j|<dS)z,Replace a values for a key with a new value.Nr�rr�valuerrr�__setitem__(szmultidict.__setitem__cCs|j|=dS)zDelete all values for a key.Nrrrrr�__delitem__,szmultidict.__delitem__cCs
||jvSrrrrrr�__contains__0rzmultidict.__contains__cCs
t|j�Sr)�lenr
rrrr�__len__3rzmultidict.__len__NcCs$z|�|�WSty|YSwr)r�KeyError)rr�defaultrrr�get6s
�z
multidict.getcCs|j�|g��|�dS)z<Add a new value for a key. Does not replace existing values.N)r
�
setdefault�appendrrrr�add<sz
multidict.addcCs|j�|g�S)zObtains all values for a key.)r
r"rrrr�getall@rzmultidict.getallcCs*|j|}t|�dkrtd|��|dS)ztObtain a single value for a key.

        Raises KeyError if key not defined or it has multiple values set.
        �smultiple values for %rr)r
rr )rr�valsrrr�getoneDs
zmultidict.getonecCsdd�t�|j�D�S)NcSsi|]	\}}|t|��qSr)�list��.0�k�vrrr�
<dictcomp>Qsz+multidict.asdictoflists.<locals>.<dictcomp>)r�	iteritemsr
rrrr�
asdictoflistsPszmultidict.asdictoflistsr)�__name__�
__module__�__qualname__�__doc__rrrrrrr"r%r&r)r1rrrrr
s
r
T)�frozenc@s�eZdZdZe��Ze��Ze��Ze��Z	e��Z
e��Ze��Ze��Z
e��Ze��Ze��Ze��Ze��Ze��Ze��Ze��Ze��ZdS)�
parsedrequestztRepresents a parsed WSGI request.

    Contains both parsed parameters as well as a handle on the input stream.
    N)r2r3r4r5r�ib�method�url�baseurl�
advertisedurl�advertisedbaseurl�	urlscheme�
remoteuser�
remotehost�apppath�
dispatchparts�dispatchpath�reponame�querystring�qsparams�headers�bodyfh�rawenvrrrrr7Ts&r7Ncs�tjrdd���fdd�t�|�D�}|s|�d�}|r!t�|�}|dd}|r2|jr2|jd}n|}dd	�}|�d
�rD||d
7}n
||d7}|||d�}|r�|jr�||j7}|jrb|j}n|jd
krm|jsmd}n|jdkrx|jsxd}n|d}|||�}n
||d7}|||d�}|}|}	|t	j
�|�dd��7}|t	j
�|�dd��7}|r�|jp�d}
|
r�|
�
d�s�d|
}
|t	j
�|
�7}n|t	j
�|�dd��7}|t	j
�|�dd��7}|�d�r�|d|d7}|d|d7}|�r	|jp�d}|�r|�
d��sd|}n|�dd�}|�rjd|�d�}|�d��s$t�d��|d�
|��s7t�d|d|f��|dt|�d�}
|
�rU|
�
d��sUt�d|d|f��|�d�|}|
�d��d�}d�|�}
n&d|v�r�|d�d��r�|d�d��d�}d�|�}
n	g}d}
ng}d}
|�dd�}t�}t	j
j|dd�D]\}}|�||��q�g}t�|�D]\}}|�
d��r�|�|td�d��dd�|f��q�d d!lm}|�|�}d"|v�r�d#|v�r�|d"|d$<d%|v�r�d&|v�r�|d%|d'<|du�r|d(}d$|v�rt	�|t|d$�pd)��}td>id*|d+�d,|�d-|�d.|�d/|	�d0|d�d1|�d2��d3|�d4��d5|�d6|�d7|
�d8|�d9|�d:|�d;|�d<|�d=|��S)?a�Parse URL components from environment variables.

    WSGI defines request attributes via environment variables. This function
    parses the environment variables into a data structure.

    If ``reponame`` is defined, the leading path components matching that
    string are effectively shifted from ``PATH_INFO`` to ``SCRIPT_NAME``.
    This simulates the world view of a WSGI application that processes
    requests from the base URL of a repo.

    If ``altbaseurl`` (typically comes from ``web.baseurl`` config option)
    is defined, it is used - instead of the WSGI environment variables - for
    constructing URL components up to and including the WSGI application path.
    For example, if the current WSGI application is at ``/repo`` and a request
    is made to ``/rev/@`` with this argument set to
    ``http://myserver:9000/prefix``, the URL and path components will resolve as
    if the request were to ``http://myserver:9000/prefix/rev/@``. In other
    words, ``wsgi.url_scheme``, ``SERVER_NAME``, ``SERVER_PORT``, and
    ``SCRIPT_NAME`` are all effectively replaced by components from this URL.

    ``bodyfh`` can be used to specify a file object to read the request body
    from. If not defined, ``wsgi.input`` from the environment dict is used.
    cSs(t|t�s|Stjrt�|�St�|�Sr)�
isinstance�strr�	iswindowsr�
strtolocal�fsencode)�srrr�tobytes�s



z$parserequestfromenv.<locals>.tobytescsi|]\}}�|��|��qSrrr+�rPrrr/�sz'parserequestfromenv.<locals>.<dictcomp>s	REPO_NAMEswsgi.url_schemes://cSs:|�d�r|dkr|d|7}|S|dkr|d|7}|S)Nshttps://�443�:�80)�
startswith)rO�portrrr�addport�s
�z$parserequestfromenv.<locals>.addports	HTTP_HOSTsSERVER_NAMEsSERVER_PORTshttprTshttpsrRsSCRIPT_NAME�s	PATH_INFO�/sQUERY_STRING�?sreponame requires PATH_INFOs0PATH_INFO does not begin with repo name: %s (%s)NsDreponame prefix of PATH_INFO does not end at path delimiter: %s (%s)T)�keep_blank_valuessHTTP_�_�-r'��wsgiheaderssCONTENT_LENGTHsHTTP_CONTENT_LENGTH�Content-LengthsCONTENT_TYPEsHTTP_CONTENT_TYPEsContent-Types
wsgi.input�0r9sREQUEST_METHODr:r;r<r=r>r?sREMOTE_USERr@sREMOTE_HOSTrArBrCrDrErFrGrHrIr) r�ispy3r0r"r	r:�scheme�hostrVr�urlreq�quote�pathrU�stripr�ProgrammingErrorr�rstrip�split�joinr
�parseqslr%r$�replace�r_�Headers�cappedreader�intr7)�envrD�
altbaseurlrH�fullurl�advertisedfullurlrWrVr;r=rgrA�
repoprefixrCrBrErFr-r.rGr_rrQr�parserequestfromenv�s#









�

��
��
"�


�������
�
�	�
���
�����rxc@s0eZdZdZdd�Zdd�Zdd�Zdd	�Zd
S)�offsettrackingwritera�A file object like object that is append only and tracks write count.

    Instances are bound to a callable. This callable is called with data
    whenever a ``write()`` is attempted.

    Instances track the amount of written data so they can answer ``tell()``
    requests.

    The intent of this class is to wrap the ``write()`` function returned by
    a WSGI ``start_response()`` function. Since ``write()`` is a callable and
    not a file object, it doesn't implement other file object methods.
    cCs||_d|_dS)Nr)�_write�_offset)r�writefnrrrrws
zoffsettrackingwriter.__init__cCs:|�|�}|dur|jt|�7_dS|j|7_dSr)rzr{r)rrO�resrrr�write{s
zoffsettrackingwriter.writecCsdSrrrrrr�flush�szoffsettrackingwriter.flushcCs|jSr)r{rrrr�tell�szoffsettrackingwriter.tellN)r2r3r4r5rr~rr�rrrrryis
ryc@sHeZdZdZdd�Zdd�Zdd�Zdd	�Zd
d�Zdd
�Z	dd�Z
dS)�wsgiresponseaPRepresents a response to a WSGI request.

    A response consists of a status line, headers, and a body.

    Consumers must populate the ``status`` and ``headers`` fields and
    make a call to a ``setbody*()`` method before the response can be
    issued.

    When it is time to start sending the response over the wire,
    ``sendresponse()`` is called. It handles emitting the header portion
    of the response message. It then yields chunks of body data to be
    written to the peer. Typically, the WSGI application itself calls
    and returns the value from ``sendresponse()``.
    cCsL||_||_d|_ddlm}|�g�|_d|_d|_d|_	d|_
d|_dS)z�Create an empty response tied to a specific request.

        ``req`` is a ``parsedrequest``. ``startresponse`` is the
        ``start_response`` function passed to the WSGI application.
        Nr'r^F)�_req�_startresponse�statusror_rprG�
_bodybytes�_bodygen�_bodywillwrite�_started�_bodywritefn)r�req�
startresponser_rrrr�s
zwsgiresponse.__init__cCs(|jdus
|jdus
|jrt�d��dS)Ns!cannot define body multiple times)r�r�r�rrirrrr�_verifybody�s

�
�zwsgiresponse._verifybodycCs$|��||_dt|�|jd<dS)ztDefine the response body as static bytes.

        The empty string signals that there is no response body.
        s%dr`N)r�r�rrG)r�brrr�setbodybytes�szwsgiresponse.setbodybytescCs|��||_dS)z1Define the response body as a generator of bytes.N)r�r�)r�genrrr�
setbodygen�s
zwsgiresponse.setbodygencCs|��d|_dS)aSignal an intent to use write() to emit the response body.

        **This is the least preferred way to send a body.**

        It is preferred for WSGI applications to emit a generator of chunks
        constituting the response body. However, some consumers can't emit
        data this way. So, WSGI provides a way to obtain a ``write(data)``
        function that can be used to synchronously perform an unbuffered
        write.

        Calling this function signals an intent to produce the body in this
        manner.
        TN)r�r�rrrr�setbodywillwrite�s
zwsgiresponse.setbodywillwriteccs��|jr	t�d��d|_|jst�d��|jdur&|jdur&|js&t�d��|j�d�r]|j�	d�dkr8|jd=d	d
�|j�
�D�}|rPt�dd�t|����|jdusX|jr]t�d
��d}d}|j
j�	dd���dkrnn|j
jdvrun
t|j
jtj�s�d}nd}|r�d|jd<|r�t|j
jtj�s�J�	|j
j�d�}|s�nq�dd�|j��D�}|�t�|j�|�}|jr�|jVdS|jr�|jD]}t|t�r�t|�}|Vq�dS|jr�||_dSt�d�dS)z�Send the generated response to the client.

        Before this is called, ``status`` must be set and one of
        ``setbodybytes()`` or ``setbodygen()`` must be called.

        Calling this method multiple times is not allowed.
        s$sendresponse() called multiple timesTsstatus line not definedNsresponse body not defineds304 r`racSsh|]
}|��dvr|�qS))sdatesetagsexpiress
cache-controlscontent-locationscontent-security-policysvary)�lower)r,r-rrr�	<setcomp>�s��z,wsgiresponse.sendresponse.<locals>.<setcomp>s"illegal header on 304 response: %ss, s,must use setbodybytes('') with 304 responsesFsExpectrXs100-continue)sPOSTsPUTsCloses
Connectioni�cSs$g|]\}}t�|�t�|�f�qSr)r�strurlr+rrr�
<listcomp>Es��z-wsgiresponse.sendresponse.<locals>.<listcomp>sdo not know how to send body)r�rrir�r�r�r�rUrGr"�keysrl�sortedr�r�r9rJrHrrq�read�itemsr�r�sysstr�	bytearray�bytesr�)r�
badheaders�drain�close�chunk�
strheadersr~rrr�sendresponse�s|��


�
	����
��

�
zwsgiresponse.sendresponsecCs4|jst�d��|jst�d��|jsJ�t|j�S)a�Obtain a file object like object representing the response body.

        For this to work, you must call ``setbodywillwrite()`` and then
        ``sendresponse()`` first. ``sendresponse()`` is a generator and the
        function won't run to completion unless the generator is advanced. The
        generator yields not items. The easiest way to consume it is with
        ``list(res.sendresponse())``, which should resolve to an empty list -
        ``[]``.
        s"must call setbodywillwrite() firstsWmust call sendresponse() first; did you remember to consume it since it is a generator?)r�rrir�r�ryrrrr�getbodyfile[s

�

zwsgiresponse.getbodyfileN)r2r3r4r5rr�r�r�r�r�r�rrrrr��s	r�cs|���fdd�}|S)z{For compatibility with old CGI scripts. A plain hgweb() or hgwebdir()
    can and should now be used as a WSGI application.cs
�||�Srr)rs�respond��applicationrr�run_wsgixrz!wsgiapplication.<locals>.run_wsgir)�	app_makerr�rr�r�wsgiapplicationssr�)NNN)�
__future__r�
thirdpartyrrorrrr�utilsr	�objectr
rOr7rxryr�r�rrrr�<module>s
;
0e!j