{D< ddlmZddlmZmZmZmZddlmZGddZ ejdGdd Z dd Z Gd d Z GddZdZy ))attr)encodingerrorpycompatutil)urlutilcTeZdZdZdZdZdZdZdZdZ dd Z d Z d Z d Z d Zy) multidictzA 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. ci|_yN_itemsselfs ;usr/lib/python3.12/site-packages/mercurial/hgweb/request.py__init__zmultidict.__init__ s  c&|j|dS)z%Returns the last set value for a key.r rkeys r __getitem__zmultidict.__getitem__#s{{3##rc$|g|j|<y)z,Replace a values for a key with a new value.Nr rrvalues r __setitem__zmultidict.__setitem__'s!7 Crc|j|=y)zDelete all values for a key.Nr rs r __delitem__zmultidict.__delitem__+s KK rc||jvSr r rs r __contains__zmultidict.__contains__/sdkk!!rc,t|jSr )lenrrs r__len__zmultidict.__len__2s4;;rNcH |j|S#t$r|cYSwxYwr )rKeyError)rrdefaults rgetz multidict.get5s, ##C( ( N s  !!cZ|jj|gj|y)z$#"  6( .tobytess@!S!H   &&q) )$$Q' 'rs REPO_NAMEswsgi.url_schemes://c`|jdr|dk7r|d|zz }|S|dk7r|d|zz }|S)Nshttps://443:80) startswith)rZports raddportz$parserequestfromenv..addportsF << $v~TD[  u}TD[ rs HTTP_HOSTs SERVER_NAMEs SERVER_PORTshttpr_shttpsr]s SCRIPT_NAMErs PATH_INFO/s QUERY_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_LENGTHContent-Lengths CONTENT_TYPEsHTTP_CONTENT_TYPEs Content-Types wsgi.input0rBsREQUEST_METHODrCrDrErFrGrHs REMOTE_USERrIs REMOTE_HOSTrJrKrLrMrNrOrPrQrRr=)r4r'rrCschemehostrarurlreqquotepathr`striprProgrammingErrorr"rstripsplitjoinr parseqslr+r*replaceriHeaders cappedreaderintr@)envrM altbaseurlrQr[r6r7fullurladvertisedfullurlrbrarDrFrprJ repoprefixrLrKrNrOrPris rparserequestfromenvrsF (/2iik :kda71:wqz !kC : 77<([[, $%.Gj''&--6# ww|3|$$3~&&'3~#67jooZ__, ????D   ' )*//D   ( *:??D~&D#$5t<S00#$5s>7JKG) t{{  !=>>G t{{  s!;<$?F  $%    (   ,   ()  77>* 77>*  $ "       ! "#  ;sV c(eZdZdZdZdZdZdZy)offsettrackingwriteraA 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 ||_d|_y)Nr0)_write_offset)rwritefns rrzoffsettrackingwriter.__init__ts  rc|j|}||xjt|z c_y|xj|z c_yr )rrr")rrZress rwritezoffsettrackingwriter.writexs4kk!n ; LLCF "L LLC Lrcyr r=rs rflushzoffsettrackingwriter.flushs rc|jSr )rrs rtellzoffsettrackingwriter.tells ||rN)r9r:r;r<rrrrr=rrrrfs   rrc:eZdZdZdZdZdZdZdZdZ dZ y ) 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()``. c||_||_d|_ddlm}|j g|_d|_d|_d|_ d|_ d|_ y)zCreate an empty response tied to a specific request. ``req`` is a ``parsedrequest``. ``startresponse`` is the ``start_response`` function passed to the WSGI application. Nr/rhF) _req_startresponsestatusrxriryrP _bodybytes_bodygen_bodywillwrite_started _bodywritefn)rreq startresponseris rrzwsgiresponse.__init__sT  + !"**2.  #  rcv|j|j |jrtjdy)Ns!cannot define body multiple times)rrrrrrrs r _verifybodyzwsgiresponse._verifybodys6 OO '}}(""(()MN N#rch|j||_dt|z|jd<y)ztDefine the response body as static bytes. The empty string signals that there is no response body. s%drjN)rrr"rP)rbs r setbodybyteszwsgiresponse.setbodybytess. */#a&. &'rc2|j||_y)z1Define the response body as a generator of bytes.N)rr)rgens r setbodygenzwsgiresponse.setbodygens  rc2|jd|_y)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)rrrs rsetbodywillwritezwsgiresponse.setbodywillwrites "rc#:K|jrtjdd|_|jstjd|jF|j :|j s.|jjdk7rtjd|jjdr|jjdd k(r |jd=|jjDchc]}|jd vr|}}|r0tjd d jt|z|j |j rtjd d}d}|jjjddjdk(rnL|jjdvrn3t!|jj"t$j&sd}nd}|rd|jd<|rZt!|jj"t$j&sJ |jj"j)d}|sn)|jj+Dcgc]/\}}t-j.|t-j.|f1}}}|j1t-j2|j|}|jr|jy|j r1|j D]!}t!|t4r t7|}|#y|j r||_y|jjdk(rytjdycc}wcc}}ww)zSend 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 definedNsHEADsresponse body not defineds304 rjrk)sdatesetagsexpiress cache-controlscontent-locationscontent-security-policysvarys"illegal header on 304 response: %ss, s,must use setbodybytes('') with 304 responsesFsExpectrs 100-continue)sPOSTsPUTsCloses Connectionisdo not know how to send body)rrrrrrrrrrBr`rPr'keyslowerrusortedrUrQrrzreadr4rstrurlrsysstr bytearraybytesr) rr6 badheadersdrainclosechunkr7 strheadersrs r sendresponsezwsgiresponse.sendresponses% ==((7  {{(()CD D OO # %''   G+(()EF F ;; ! !' *|| 12d:LL!23 **, ,A779 ,  ,,9jj !345 }}(D,?,?,,C 99   C 0 6 6 8O K YY  %6 6 dii..0A0AB *2DLL ' dii..0A0AB BB ((--e4 **, ,1__Q !3 4,  ##HOODKK$@*M ??// ! ]]eY/!%LE ' %D  YY   (   " "#B C} P s C>NNE3N4NCNc|jstjd|jstjd|jsJt |jS)aObtain 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?)rrrrrrrrs r getbodyfilezwsgiresponse.getbodyfile[s`""(()NO O}}((#      #D$5$566rN) r9r:r;r<rrrrrrrr=rrrrs. !(O9 #"GDR7rrc |fd}|S)z{For compatibility with old CGI scripts. A plain hgweb() or hgwebdir() can and should now be used as a WSGI application.c||Sr r=)r|respond applications rrun_wsgiz!wsgiapplication..run_wsgixs3((rr=) app_makerrrs @rwsgiapplicationrss+K) Or)NNN) thirdpartyrrxrrrrutilsrr rZr@rrrrr=rrrsm  8<8