U iÛf¥Tã @sdZddlmZmZmZddlmZddlZddlZddl Z dddd d d gZ d d dddddgZ dddddddddddddg Z dd „Z d!d"d#d$d%d&d'd(d)d*h jZd+d,„Zd-d „ZGd.d„dƒZGd/d„deƒZGd0d„deƒZGd1d „d eƒZGd2d „d eƒZdS)3z/Base classes for server/gateway implementationsé)Ú FileWrapperÚ guess_schemeÚ is_hop_by_hop)ÚHeaderséNÚ BaseHandlerÚ SimpleHandlerÚBaseCGIHandlerÚ CGIHandlerÚ IISCGIHandlerÚ read_environZMonZTueZWedZThuZFriZSatZSunZJanZFebZMarZAprZMayZJunZJulZAugZSepZOctZNovZDecc Cs:t |¡\ }}}}}}}}} dt||t|||||fS)Nz#%s, %02d %3s %4d %02d:%02d:%02d GMT)ÚtimeÚgmtimeÚ _weekdaynameÚ _monthname) Z timestampZyearZmonthZdayZhhZmmZssZwdÚyÚz©rú5/opt/alt/python38/lib64/python3.8/wsgiref/handlers.pyÚformat_date_timesÿrÚ SCRIPT_NAMEÚ PATH_INFOZ QUERY_STRINGZREQUEST_METHODZ AUTH_TYPEZ CONTENT_TYPEZCONTENT_LENGTHZHTTPSZ REMOTE_USERZ REMOTE_IDENTcCs6t|ƒp4| d¡p4| d¡p4| d¡o4t|dd…ƒS)NZHTTP_ZSSL_Z REDIRECT_é )Ú _is_requestÚ startswithÚ_needs_transcode)ÚkrrrrsÿrcCsðt ¡}d}zd d|¡Wntk r4d}YnXi}tj ¡D]¦\}}t|ƒrâtjdkrÐtj  dd¡  ¡}|  d¡rŒ| d¡  d¡}qâ|  d ¡r˜qâ|  d ¡r¼d |kr¼| d¡  d¡}qâ| |d¡  d¡}n| ||¡  d¡}|||<qD|S) z'Read environment, fixing HTTP variablesÚsurrogateescapeÚzutf-8ÚreplaceZwin32ÚSERVER_SOFTWAREzmicrosoft-iis/ú iso-8859-1zapache/z simplehttp/zpython/3) ÚsysÚgetfilesystemencodingÚencodeÚ LookupErrorÚosÚenvironÚitemsrÚplatformÚgetÚlowerrÚdecode)ÚencZescr'rÚvZsoftwarerrrr "s0    ÿþ c@s"eZdZdZdZdZdZdZdZdZ dZ e ƒZ e ZeZdZdZdgZd ZdZZdZdZd Zd d „Zd d„Zdd„Zdd„Zdd„Zdd„Zd;dd„Z dd„Z!dd„Z"dd„Z#dd „Z$d!d"„Z%d#d$„Z&d%d&„Z'd'd(„Z(d)d*„Z)d+d,„Z*d-d.„Z+d/d0„Z,d1d2„Z-d3d4„Z.d5d6„Z/d7d8„Z0d9d:„Z1dS)Send any iterable data, then close self and the iterable Subclasses intended for use in asynchronous servers will want to redefine this method, such that it sets up callbacks in the event loop to iterate over the data, and to call 'self.close()' once the response is finished. r7N)Úresult_is_fileÚsendfiler1ÚwriteÚfinish_contentÚhasattrr7©r8Údatarrrr2­s     zBaseHandler.finish_responsecCs t|jƒS)z Return the URL scheme being used)rr'©r8rrrrAÇszBaseHandler.get_schemec CsJzt|jƒ}Wntttfk r(YnX|dkrFt|jƒ|jd<dSdS)z@Compute Content-Length or switch to chunked encoding if possiblerúContent-LengthN)Úlenr1Ú TypeErrorÚAttributeErrorÚNotImplementedErrorÚstrÚ bytes_sentÚheaders)r8ZblocksrrrÚset_content_lengthÌszBaseHandler.set_content_lengthcCsd|jkr| ¡dS)zqMake any necessary header changes or defaults Subclasses can extend this to add other defaults. rQN)rXrYrPrrrÚcleanup_headersÙs zBaseHandler.cleanup_headerscCsh|r2z$|jr&|d|dƒ |d¡‚W5d}Xn|jdk rDtdƒ‚||_| |¡|_| |d¡}|jS)z4'start_response()' callable as specified by PEP 3333NrrézHeaders already set!ZStatus)Ú headers_sentÚwith_tracebackrXÚAssertionErrorÚstatusÚ headers_classÚ_convert_string_typerK)r8r_rXÚexc_inforrrr0ás   zBaseHandler.start_responsecCs(t|ƒtkr|Std |t|ƒ¡ƒ‚dS)zConvert/check value type.z!{0} must be of type str (got {1})N)ÚtyperVr^ÚformatÚrepr)r8ÚvalueÚtitlerrrraþs  ÿz BaseHandler._convert_string_typecCs’|jrx| ¡rŽ| d|j|jf d¡¡d|jkrP| dtt ¡ƒ d¡¡|j rŽd|jkrŽ| d|j  d¡¡n| d|j d¡¡dS) z6Transmit version/status/date/server, via self._write()z HTTP/%s %s r!ZDatez Date: %s ZServerz Server: %s z Status: %s N) rEÚclient_is_modernÚ_writeÚ http_versionr_r$rXrr rFrPrrrÚ send_preambles ÿzBaseHandler.send_preamblecCsR|jstdƒ‚n,|js*t|ƒ|_| ¡n|jt|ƒ7_| |¡| ¡dS)z+'write()' callable as specified by PEP 3333zwrite() before start_response()N)r_r^r\rRrWÚ send_headersriÚ_flushrNrrrrKs    zBaseHandler.writecCsdS)aPlatform-specific file transmission Override this method in subclasses to support platform-specific file transmission. It is only called if the application's return iterable ('self.result') is an instance of 'self.wsgi_file_wrapper'. This method should return a true value if it was able to actually transmit the wrapped file-like object using a platform-specific approach. It should return a false value if normal iteration should be used instead. An exception can be raised to indicate that transmission was attempted, but failed. NOTE: this method should call 'self.send_headers()' if 'self.headers_sent' is false and it is going to attempt direct transmission of the file. FrrPrrrrJ)szBaseHandler.sendfilecCs"|js|j dd¡| ¡ndS)z.Ensure headers and content have both been sentrQÚ0N)r\rXrGrlrPrrrrL>s zBaseHandler.finish_contentc CsFzt|jdƒr|j ¡W5d|_|_|_|_d|_d|_XdS)z„Close the iterable (if needed) and reset all instance vars Subclasses may want to also drop the client connection. NrFr7)r1rXr_r'rWr\rMr7rPrrrr7Hs  zBaseHandler.closecCs8| ¡d|_|jr| ¡r4| ¡| t|jƒ¡dS)z1Transmit headers to the client, via self._write()TN)rZr\rErhrkriÚbytesrXrPrrrrlUs zBaseHandler.send_headerscCs|j}|dk ot|j|ƒS)z@True if 'self.result' is an instance of 'self.wsgi_file_wrapper'N)rDÚ isinstancer1)r8ÚwrapperrrrrI^szBaseHandler.result_is_filecCs|jd ¡dkS)z,True if client can accept status and headersZSERVER_PROTOCOLzHTTP/0.9)r'ÚupperrPrrrrhdszBaseHandler.client_is_moderncCsJz>ddlm}| ¡}||d|d|d|j|ƒ| ¡W5d}XdS)zLog the 'exc_info' tuple in the server log Subclasses may override to retarget the output or change its format. Nr)Úprint_exceptionrr[)Ú tracebackrsr>Útraceback_limitÚflush)r8rbrsÚstderrrrrÚ log_exceptionis þ zBaseHandler.log_exceptioncCs2| t ¡¡|js.| |j|j¡|_| ¡dS)z>Log current error, and send error output to client if possibleN) rxr"rbr\Ú error_outputr'r0r1r2rPrrrr6yszBaseHandler.handle_errorcCs$||j|jdd…t ¡ƒ|jgS)aZWSGI mini-app to create error output By default, this just uses the 'error_status', 'error_headers', and 'error_body' attributes to generate an output page. It can be overridden in a subclass to dynamically generate diagnostics, choose an appropriate message for the user's preferred language, etc. Note, however, that it's not recommended from a security perspective to spit out diagnostics to any old user; ideally, you should have to do something special to enable diagnostic output, which is why we don't include any here! N)Ú error_statusÚ error_headersr"rbÚ error_body)r8r'r0rrrrys zBaseHandler.error_outputcCst‚dS)aOverride in subclass to buffer data for send to client It's okay if this method actually transmits the data; BaseHandler just separates write and flush operations for greater efficiency when the underlying system actually has such a distinction. N©rUrNrrrri”szBaseHandler._writecCst‚dS)z¬Override in subclass to force sending of recent '_write()' calls It's okay if this method is a no-op (i.e., if '_write()' actually sends the data. Nr}rPrrrrmszBaseHandler._flushcCst‚dS)z4Override in subclass to return suitable 'wsgi.input'Nr}rPrrrr=¥szBaseHandler.get_stdincCst‚dS)z5Override in subclass to return suitable 'wsgi.errors'Nr}rPrrrr>©szBaseHandler.get_stderrcCst‚dS)z>Override in subclass to insert CGI variables in 'self.environ'Nr}rPrrrr<­szBaseHandler.add_cgi_vars)N)2Ú__name__Ú __module__Ú __qualname__Ú__doc__r?rBrCr@rErjrFr r:rrDrr`rurzr{r|r_r1r\rXrWr9r/r2rArYrZr0rarkrKrJrLr7rlrIrhrxr6ryrirmr=r>r<rrrrr^sV      c@sBeZdZdZddd„Zdd„Zdd „Zd d „Zd d „Zdd„Z dS)raqHandler that's just initialized with streams, environment, etc. This handler subclass is intended for synchronous HTTP/1.0 origin servers, and handles sending the entire response output, given the correct inputs. Usage:: handler = SimpleHandler( inp,out,err,env, multithread=False, multiprocess=True ) handler.run(app)TFcCs(||_||_||_||_||_||_dS©N)ÚstdinÚstdoutrwÚbase_envrBrC)r8rƒr„rwr'Ú multithreadÚ multiprocessrrrÚ__init__¿s zSimpleHandler.__init__cCs|jSr‚)rƒrPrrrr=ÉszSimpleHandler.get_stdincCs|jSr‚)rwrPrrrr>ÌszSimpleHandler.get_stderrcCs|j |j¡dSr‚)r'Úupdater…rPrrrr<ÏszSimpleHandler.add_cgi_varscCs^|j |¡}|dks |t|ƒkr$dSddlm}|dtƒ||d…}|sLqZ|j |¡}q:dS)Nr)Úwarnz9SimpleHandler.stdout.write() should not do partial writes)r„rKrRÚwarningsrŠÚDeprecationWarning)r8rOr1rŠrrrriÒs  ÿ zSimpleHandler._writecCs|j ¡|jj|_dSr‚)r„rvrmrPrrrrmßs zSimpleHandler._flushN)TF) r~rr€rrˆr=r>r<rirmrrrrr²s ÿ  c@seZdZdZdZdS)r aÚCGI-like systems using input/output/error streams and environ mapping Usage:: handler = BaseCGIHandler(inp,out,err,env) handler.run(app) This handler class is useful for gateway protocols like ReadyExec and FastCGI, that have usable input/output/error streams and an environment mapping. It's also the base class for CGIHandler, which just uses sys.stdin, os.environ, and so on. The constructor also takes keyword arguments 'multithread' and 'multiprocess' (defaulting to 'True' and 'False' respectively) to control the configuration sent to the application. It sets 'origin_server' to False (to enable CGI-like output), and assumes that 'wsgi.run_once' is False. FN)r~rr€rrErrrrr äsc@s eZdZdZdZiZdd„ZdS)r aéCGI-based invocation via sys.stdin/stdout/stderr and os.environ Usage:: CGIHandler().run(app) The difference between this class and BaseCGIHandler is that it always uses 'wsgi.run_once' of 'True', 'wsgi.multithread' of 'False', and 'wsgi.multiprocess' of 'True'. It does not take any initialization parameters, but always uses 'sys.stdin', 'os.environ', and friends. If you need to override any of these parameters, use BaseCGIHandler instead. Tc Cs(tj|tjjtjjtjtƒddddS)NFT©r†r‡)r rˆr"rƒÚbufferr„rwr rPrrrrˆsþzCGIHandler.__init__N©r~rr€rr@r:rˆrrrrr üsc@s eZdZdZdZiZdd„ZdS)r aCGI-based invocation with workaround for IIS path bug This handler should be used in preference to CGIHandler when deploying on Microsoft IIS without having set the config allowPathInfo option (IIS>=7) or metabase allowPathInfoForScriptMappings (IIS<7). Tc Csjtƒ}| dd¡}| dd¡}|d |d¡rD|t|ƒd…|d<tj|tjjtj jtj |ddddS)Nrrrú/FTr) r r*rrRr rˆr"rƒrŽr„rw)r8r'ÚpathZscriptrrrrˆ2s  þzIISCGIHandler.__init__Nrrrrrr s)rÚutilrrrrXrr"r&r Ú__all__rrrÚ __contains__rrr rrr r r rrrrÚs\ þþþ<V2