a  ze:@sdZdgZddlZddlZddlZedZedZGdddeZ dd Z d d Z d dZ Gd ddZ GdddZGdddZGdddZGdddZddZddZddZddZdd Zd!d"Zd#d$Zd%d&ZdS)'a& Middleware to check for obedience to the WSGI specification. Some of the things this checks: * Signature of the application and start_response (including that keyword arguments are not used). * Environment checks: - Environment is a dictionary (and not a subclass). - That all the required keys are in the environment: REQUEST_METHOD, SERVER_NAME, SERVER_PORT, wsgi.version, wsgi.input, wsgi.errors, wsgi.multithread, wsgi.multiprocess, wsgi.run_once - That HTTP_CONTENT_TYPE and HTTP_CONTENT_LENGTH are not in the environment (these headers should appear as CONTENT_LENGTH and CONTENT_TYPE). - Warns if QUERY_STRING is missing, as the cgi module acts unpredictably in that case. - That CGI-style variables (that don't contain a .) have (non-unicode) string values - That wsgi.version is a tuple - That wsgi.url_scheme is 'http' or 'https' (@@: is this too restrictive?) - Warns if the REQUEST_METHOD is not known (@@: probably too restrictive). - That SCRIPT_NAME and PATH_INFO are empty or start with / - That at least one of SCRIPT_NAME or PATH_INFO are set. - That CONTENT_LENGTH is a positive integer. - That SCRIPT_NAME is not '/' (it should be '', and PATH_INFO should be '/'). - That wsgi.input has the methods read, readline, readlines, and __iter__ - That wsgi.errors has the methods flush, write, writelines * The status is a string, contains a space, starts with an integer, and that integer is in range (> 100). * That the headers is a list (not a subclass, not another kind of sequence). * That the items of the headers are tuples of strings. * That there is no 'status' header (that is used in CGI, but not in WSGI). * That the headers don't contain newlines or colons, end in _ or -, or contain characters codes below 037. * That Content-Type is given if there is content (CGI often has a default content type, but WSGI does not). * That no Content-Type is given when there is no content (@@: is this too restrictive?) * That the exc_info argument to start_response is a tuple or None. * That all calls to the writer are with strings, and no other methods on the writer are accessed. * That wsgi.input is used properly: - .read() is called with exactly one argument - That it returns a string - That readline, readlines, and __iter__ return strings - That .close() is not called - No other methods are provided * That wsgi.errors is used properly: - .write() and .writelines() is called with a string - That .close() is not called, and no other methods are provided. * The response iterator: - That it is not a string (it should be a list of a single string; a string will work, but perform horribly). - That .__next__() returns a string - That the iterator is not iterated over until start_response has been called (that can signal either a server or application error). - That .close() is called (doesn't raise exception, only prints to sys.stderr, because we only know it isn't called when the object is garbage collected). validatorNz^[a-zA-Z][a-zA-Z0-9\-_]*$z [\000-\037]c@seZdZdZdS) WSGIWarningz: Raised in response to WSGI-spec-related warnings N)__name__ __module__ __qualname____doc__rrD/opt/bitninja-python-dojo/embedded/lib/python3.9/wsgiref/validate.pyrysrcGs|s t|dSN)AssertionError)condargsrrr assert_~srcCs(t|tur|Std|t|dS)Nz!{0} must be of type str (got {1}))typestrr formatrepr)valuetitlerrr check_string_types  rcsfdd}|S)a When applied between a WSGI server and a WSGI application, this middleware will check for WSGI compliance on a number of levels. This middleware does not modify the request or response in any way, but will raise an AssertionError if anything seems off (except for a failure to close the application iterator, which will be printed to stderr -- there's no way to raise an exception at that point). cstt|dkdt| d|\}t|gfdd}t|d|d<t|d|d<||}t|duoz|dkd t|t|S) NzTwo arguments requiredNo keyword arguments allowedcstt|dkpt|dkd|ft| d|d}|d}t|dkrV|d}nd}t|t|t||t|dt|S)NrzInvalid number of arguments: %srr)rlen check_status check_headerscheck_content_typecheck_exc_infoappend WriteWrapper)r kwstatusheadersexc_infoZstart_responseZstart_response_startedrr start_response_wrappers     z;validator..lint_app..start_response_wrapper wsgi.input wsgi.errorsFz>The application must return an iterator, if only an empty list)rr check_environ InputWrapper ErrorWrappercheck_iteratorIteratorWrapper)r r!environr&iterator applicationr%r lint_apps  zvalidator..lint_appr)r1r2rr0r rs )c@s<eZdZddZddZddZddZd d Zd d Zd S)r*cCs ||_dSr )input)self wsgi_inputrrr __init__szInputWrapper.__init__cGs0tt|dk|jj|}tt|tu|SNr)rrr3readrbytesr4r vrrr r8s zInputWrapper.readcGs0tt|dk|jj|}tt|tu|Sr7)rrr3readlinerr9r:rrr r<s zInputWrapper.readlinecGsJtt|dk|jj|}tt|tu|D]}tt|tuq0|Sr7)rrr3 readlinesrlistr9)r4r lineslinerrr r=s  zInputWrapper.readlinesccs|}|sdS|VqdSr )r<)r4r@rrr __iter__szInputWrapper.__iter__cCstdddS)Nrz input.close() must not be calledrr4rrr closeszInputWrapper.closeN) rrrr6r8r<r=rArDrrrr r*s r*c@s4eZdZddZddZddZddZd d Zd S) r+cCs ||_dSr )errors)r4 wsgi_errorsrrr r6szErrorWrapper.__init__cCs tt|tu|j|dSr )rrrrEwriter4srrr rGszErrorWrapper.writecCs|jdSr )rEflushrCrrr rJszErrorWrapper.flushcCs|D]}||qdSr )rG)r4seqr@rrr writelinesszErrorWrapper.writelinescCstdddS)Nrz!errors.close() must not be calledrBrCrrr rDszErrorWrapper.closeN)rrrr6rGrJrLrDrrrr r+s r+c@seZdZddZddZdS)r cCs ||_dSr )writer)r4Z wsgi_writerrrr r6szWriteWrapper.__init__cCstt|tu||dSr )rrr9rMrHrrr __call__szWriteWrapper.__call__N)rrrr6rNrrrr r sr c@seZdZddZddZdS)PartialIteratorWrappercCs ||_dSr r/)r4 wsgi_iteratorrrr r6szPartialIteratorWrapper.__init__cCs t|jdSr )r-r/rCrrr rAszPartialIteratorWrapper.__iter__N)rrrr6rArrrr rOsrOc@s4eZdZddZddZddZddZd d Zd S) r-cCs ||_t||_d|_||_dS)NF)original_iteratoriterr/closedcheck_start_response)r4rQrUrrr r6 s zIteratorWrapper.__init__cCs|Sr rrCrrr rAszIteratorWrapper.__iter__cCsTt|j dt|j}t|tur4tdd|f|jdurPt|jdd|_|S)NzIterator read after closedFz$Iterator yielded non-bytestring (%r)zjThe application returns and we started iterating over its body, but start_response has not yet been called)rrTnextr/rr9rU)r4r;rrr __next__s   zIteratorWrapper.__next__cCs d|_t|jdr|jdS)NTrD)rThasattrrRrDrCrrr rDs zIteratorWrapper.closecCs"|jstjdt|jddS)Nz/Iterator garbage collected without being closed)rTsysstderrrGrrCrrr __del__#szIteratorWrapper.__del__N)rrrr6rArWrDr[rrrr r-s  r-cCstt|tudt||fdD]}t||vd|fq"dD]"}t||vd||ddfq@d|vrxtdt|D]:}d |vrqtt||tud |t||||fqtt|d tud |d ft|d dvd|d t |dt |d|ddvr0td|dtt| d pL|d dd|dt| d pv|d dd|d| drtt |ddkd|d| dstd|vdt| ddkddS)Nz:Environment is not of the right type: %r (environment: %r)) REQUEST_METHODZ SERVER_NAMEZ SERVER_PORT wsgi.versionr'r(zwsgi.multithreadzwsgi.multiprocessz wsgi.run_oncez$Environment missing required key: %r)ZHTTP_CONTENT_TYPEZHTTP_CONTENT_LENGTHz8Environment should not have the key: %s (use %s instead)Z QUERY_STRINGzQUERY_STRING is not in the WSGI environment; the cgi module will use sys.argv when this variable is missing, so application errors are more likely.z9Environmental variable %s is not a string: %r (value: %r)r]z#wsgi.version should be a tuple (%r)zwsgi.url_scheme)httphttpszwsgi.url_scheme unknown: %rr'r(r\)GETZHEADZPOSTZOPTIONSZPATCHPUTZDELETEZTRACEzUnknown REQUEST_METHOD: %rZ SCRIPT_NAME/z$SCRIPT_NAME doesn't start with /: %rZ PATH_INFOz"PATH_INFO doesn't start with /: %rZCONTENT_LENGTHrzInvalid CONTENT_LENGTH: %rzgOne of SCRIPT_NAME or PATH_INFO are required (PATH_INFO should at least be '/' if SCRIPT_NAME is empty)zOSCRIPT_NAME cannot be '/'; it should instead be '', and PATH_INFO should be '/')rrdictwarningswarnrkeysrtuple check_input check_errorsget startswithint)r.keyrrr r)*sx                r)cCs&dD]}tt||d||fqdS)N)r8r<r=rAz-wsgi.input (%r) doesn't have the attribute %srrX)r5attrrrr rjks  rjcCs&dD]}tt||d||fqdS)N)rJrGrLz.wsgi.errors (%r) doesn't have the attribute %srp)rFrqrrr rkqs  rkcCsvt|d}|ddd}tt|dkd|t|}t|dkd|t|dksb|dd krrtd |tdS) NStatusrrrz)Status codes must be three characters: %rdzStatus code is invalid: %r zjThe status string (%r) should be a three-digit integer followed by a single space and a status explanation)rsplitrrrnrfrgr)r"Z status_codeZ status_intrrr rws  rcCstt|tud|t|f|D]}tt|tud|t|ftt|dk|\}}t|d}t|d}t|dkd|td|vod |vd |tt|d |t| d  o| d  d|t |r"tdd|t | dfq"dS)Nz%Headers (%r) must be of type list: %rz1Individual headers (%r) must be of type tuple: %rr Header namez Header valuer"zyThe Status header cannot be used; it conflicts with CGI script, and HTTP status is not given through headers (value: %r). :z,Header names may not contain ':' or '\n': %rzBad header name: %r-_z#Names may not end in '-' or '_': %rrz#Bad header value: %r (bad char: %r)) rrr>rirrlower header_researchendswithbad_header_value_regroup)r#itemnamerrrr rs>        rcCs|t|d}t|ddd}d}|D]:\}}t|d}|dkr&||vrRdStdd|q&||vrxtdd|dS) Nrrrr)i0rwz content-typezJContent-Type header found in a %s response, which must not return content.z,No Content-Type header found in headers (%s))rrnrvr|r)r"r#codeZNO_MESSAGE_BODYrrrrr rs    rcCs*t|dupt|tud|t|fdS)Nz exc_info (%r) is not a tuple: %r)rrri)r$rrr rsrcCstt|ttf ddS)NzwYou should not return a string as your application iterator, instead return a single-item list containing a bytestring.)r isinstancerr9rPrrr r,sr,)r__all__rerYrfcompiler}rWarningrrrrr*r+r rOr-r)rjrkrrrrr,rrrr s.j  7#  #A