| Server IP : 162.144.4.212 / Your IP : 216.73.216.108 Web Server : Apache System : Linux gator2125.hostgator.com 5.14.0-162.23.1.9991722448259.nf.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jul 31 18:11:45 UTC 2024 x86_64 User : cozeellc ( 2980) PHP Version : 8.3.31 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/lib64/python3.9/site-packages/mercurial/hgweb/__pycache__/ |
Upload File : |
a
�+�b
Y � @ s� d dl mZ ddlmZ ddlmZmZmZmZ ddl m
Z
G dd� de �Z ej
dd �G d
d � d e ��Zdd
d�ZG dd� de �ZG dd� de �Zdd� Zd S )� )�absolute_import� )�attr)�encoding�error�pycompat�util)�urlutilc @ sj e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd d
� Z ddd�Z
dd� Z dd� Z dd� 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.
c C s
i | _ d S �N��_items��self� r �=/usr/lib64/python3.9/site-packages/mercurial/hgweb/request.py�__init__! s zmultidict.__init__c C s | j | d S )z%Returns the last set value for a key.���r �r �keyr r r � __getitem__$ s zmultidict.__getitem__c C s |g| j |< dS )z,Replace a values for a key with a new value.Nr �r r �valuer r r � __setitem__( s zmultidict.__setitem__c C s | j |= dS )z Delete all values for a key.Nr r r r r � __delitem__, s zmultidict.__delitem__c C s
|| j v S r r r r r r � __contains__0 s zmultidict.__contains__c C s
t | j�S r )�lenr
r r r r �__len__3 s zmultidict.__len__Nc C s( z | � |�W S ty" | Y S 0 d S r )r �KeyError)r r �defaultr r r �get6 s z
multidict.getc C s | j �|g ��|� dS )z<Add a new value for a key. Does not replace existing values.N)r
�
setdefault�appendr r r r �add< s z
multidict.addc C s | j �|g �S )z Obtains all values for a key.)r
r r r r r �getall@ s zmultidict.getallc C s* | j | }t|�dkr"td| ��|d S )ztObtain a single value for a key.
Raises KeyError if key not defined or it has multiple values set.
� s multiple values for %rr )r
r r )r r Zvalsr r r �getoneD s
zmultidict.getonec C s dd� t �| j�D �S )Nc S s i | ]\}}|t |��qS r )�list��.0�k�vr r r �
<dictcomp>Q � z+multidict.asdictoflists.<locals>.<dictcomp>)r � iteritemsr
r r r r �
asdictoflistsP s zmultidict.asdictoflists)N)�__name__�
__module__� __qualname__�__doc__r r r r r r r r# r$ r& r/ r r r r r
s
r
T)�frozenc @ s� e Zd ZdZe�� Ze�� Ze�� Ze�� Z e�� Z
e�� Z e�� Z e�� 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)r0 r1 r2 r3 r Zib�method�url�baseurl�
advertisedurl�advertisedbaseurl� urlscheme�
remoteuser�
remotehost�apppath�
dispatchparts� dispatchpath�reponame� querystring�qsparams�headers�bodyfh�rawenvr r r r r5 T s$ r5 Nc s| t jr&dd� � � fdd�t �| �D �} |s4| �d�}|rBt�|�}| d d }|rd|jrd|jd }n|}dd � }| �d
�r�|| d
7 }n|| d 7 }||| d �}|�r|j�r||j7 }|jr�|j}n4|jd
kr�|js�d}n |jdkr�|js�d}n| d }|||�}n|| d 7 }||| d �}|}|} |t j
� | �dd��7 }|t j
� | �dd��7 }|�r�|j �pjd}
|
�r�|
�
d��s�d|
}
|t j
� |
�7 }n|t j
� | �dd��7 }|t j
� | �dd��7 }| �d��r�|d| d 7 }|d| d 7 }|�r"|j �pd} | �r.| �
d��s.d| } n | �dd�} |�r�d|�d� } | �d��sXt�d��| d �
| ��s~t�d| d |f ��| d t| �d� }
|
�r�|
�
d��s�t�d| d |f ��| �d�| } |
�d��d�}d�|�}
nLd| v �r(| d �d��r | d �d��d�}d�|�}
ng }d}
ng }d}
| �dd�}t� }t j
j|dd �D ]\}}|�||� �qRg }t �| �D ]8\}}|�
d ��rx|�|td �d� �d d �|f� �qxd d!lm} |� |�}d"| v �r�d#| v�r�| d" |d$< d%| v �rd&| v�r| d% |d'< |du �r>| d( }d$|v �r>t � |t |d$ �p8d)��}t | d* |||| | 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.
c S s, t | t�s| S tjr t�| �S t�| �S d S r )�
isinstance�strr Z iswindowsr Z
strtolocal�fsencode)�sr r r �tobytes� s
z$parserequestfromenv.<locals>.tobytesc s i | ]\}}� |�� |��qS r r r( �rK r r r, � r- z'parserequestfromenv.<locals>.<dictcomp>s REPO_NAMEs wsgi.url_schemes ://c S s8 | � d�r |dkr4| d| 7 } n|dkr4| d| 7 } | S )Ns https://� 443� :� 80)�
startswith)rJ �portr r r �addport� s
z$parserequestfromenv.<locals>.addports HTTP_HOSTs SERVER_NAMEs SERVER_PORTs httprO s httpsrM s SCRIPT_NAMEr- s PATH_INFO� /s QUERY_STRING� ?s reponame requires PATH_INFOs0 PATH_INFO does not begin with repo name: %s (%s)NsD reponame prefix of PATH_INFO does not end at path delimiter: %s (%s)T)�keep_blank_valuess HTTP_� _� -r% �� wsgiheaderss CONTENT_LENGTHs HTTP_CONTENT_LENGTH� Content-Lengths CONTENT_TYPEs HTTP_CONTENT_TYPEs Content-Types
wsgi.input� 0s REQUEST_METHODs REMOTE_USERs REMOTE_HOST)r6 r7 r8 r9 r: r; r< r= r> r? r@ rA rB rC rD rE rF ) r Zispy3r. r r r7 �scheme�hostrQ r Zurlreq�quote�pathrP �stripr �ProgrammingErrorr �rstrip�split�joinr
Zparseqslr# r" �replace� rY �Headers� cappedreader�intr5 )�envrA Z
altbaseurlrE ZfullurlZadvertisedfullurlrR rQ r8 r: r_ r> Z
repoprefixr@ r? rB rC r* r+ rD rY r rL r �parserequestfromenv� s� #
��
��
&
��rk c @ s0 e Zd ZdZdd� 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.
c C s || _ d| _d S )Nr )�_write�_offset)r Zwritefnr r r r w s z offsettrackingwriter.__init__c C s8 | � |�}|d u r&| jt|�7 _n| j|7 _d S r )rm rn r )r rJ �resr r r �write{ s
zoffsettrackingwriter.writec C s d S r r r r r r �flush� s zoffsettrackingwriter.flushc C s | j S r )rn r r r r �tell� s zoffsettrackingwriter.tellN)r0 r1 r2 r3 r rp rq rr r r r r rl i s
rl c @ sH e Zd ZdZdd� Zdd� Zdd� Zdd � Zd
d � Zd d
� Z dd� Z
dS )� wsgiresponseaP Represents 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()``.
c C sL || _ || _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% rX F) �_req�_startresponse�statusrf rY rg rD �
_bodybytes�_bodygen�_bodywillwrite�_started� _bodywritefn)r ZreqZ
startresponserY r r r r � s zwsgiresponse.__init__c C s( | j d us| jd us| jr$t�d��d S )Ns! cannot define body multiple times)rw rx ry r ra r r r r � _verifybody� s ���zwsgiresponse._verifybodyc C s$ | � � || _dt|� | jd< dS )ztDefine the response body as static bytes.
The empty string signals that there is no response body.
s %drZ N)r| rw r rD )r �br r r � setbodybytes� s zwsgiresponse.setbodybytesc C s | � � || _dS )z1Define the response body as a generator of bytes.N)r| rx )r �genr r r �
setbodygen� s zwsgiresponse.setbodygenc C s | � � d| _dS )a Signal 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| ry r r r r �setbodywillwrite� s z wsgiresponse.setbodywillwritec c s� | j rt�d��d| _ | js&t�d��| jdu rJ| jdu rJ| jsJt�d��| j�d�r�| j� d�dkrn| jd= d d
� | j�
� D �}|r�t�d d � t |�� ��| jdus�| jr�t�d
��d}d}| j
j� dd��� dkr�n(| j
jdvr�nt| j
jtj�s�d}nd}|�rd| jd< |�rJt| j
jtj��s.J �| j
j�d�}|�s.�qJ�q.dd� | j�� D �}| �t�| j�|�}| j�r�| jV nL| j�r�| jD ] }t|t��r�t|�}|V �q�n| j�r�|| _n
t�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 timesTs status line not definedNs response body not defineds 304 rZ r[ c S s h | ]}|� � d vr|�qS ))s dates etags expiress
cache-controls content-locations content-security-policys vary)�lower)r) r* r r r � <setcomp>� s
��z,wsgiresponse.sendresponse.<locals>.<setcomp>s" illegal header on 304 response: %ss , s, must use setbodybytes('') with 304 responsesFs Expectr- s 100-continue)s POSTs PUTs Closes
Connectioni � c S s$ g | ] \}}t �|�t �|�f�qS r )r Zstrurlr( r r r �
<listcomp>E s �z-wsgiresponse.sendresponse.<locals>.<listcomp>s do not know how to send body) rz r ra rv rw rx ry rP rD r �keysrd �sortedrt r� r6 rG rE r rh �read�itemsru r Zsysstr� bytearray�bytesr{ )r Z
badheadersZdrain�close�chunkZ
strheadersrp r r r � sendresponse� sx �
���
� ���
�
zwsgiresponse.sendresponsec C s4 | j st�d��| js t�d��| js*J �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() firstsW must call sendresponse() first; did you remember to consume it since it is a generator?)ry r ra rz r{ rl r r r r � getbodyfile[ s
�
zwsgiresponse.getbodyfileN) r0 r1 r2 r3 r r| r~ r� r� r� r� r r r r rs � s rs c s | � � � fdd�}|S )z{For compatibility with old CGI scripts. A plain hgweb() or hgwebdir()
can and should now be used as a WSGI application.c s
� | |�S r r )rj Zrespond�Z applicationr r �run_wsgix s z!wsgiapplication.<locals>.run_wsgir )Z app_makerr� r r� r �wsgiapplications s r� )NNN)Z
__future__r Z
thirdpartyr rf r r r r Zutilsr �objectr
rJ r5 rk rl rs r� r r r r �<module> s ;
0
e! j