o ?Og:@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__rr7/opt/alt/python310/lib64/python3.10/wsgiref/validate.pyrysrcGs|st|dSN)AssertionError)Zcondargsrrr assert_~sr cCs$t|tur|Std|t|)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|duo=|dkd t|t|S) NzTwo arguments requiredNo keyword arguments allowedcstt|dkp t|dkd|ft| d|d}|d}t|dkr+|d}nd}t|t|t||t|dt|S)NrzInvalid number of arguments: %srr)r len 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)r r check_environ InputWrapper ErrorWrappercheck_iteratorIteratorWrapper)r r environr%iterator applicationr$r lint_apps   zvalidator..lint_appr)r0r1rr/r rs )c@s<eZdZddZddZddZddZd d Zd d Zd S)r)cC ||_dSr )input)self wsgi_inputrrr __init__ zInputWrapper.__init__cGs0tt|dk|jj|}tt|tu|SNr)r rr3readrbytesr4r vrrr r9 zInputWrapper.readcGs0tt|dk|jj|}tt|tu|Sr8)r rr3readlinerr:r;rrr r>r=zInputWrapper.readlinecGsJtt|dk|jj|}tt|tu|D] }tt|tuq|Sr8)r rr3 readlinesrlistr:)r4r lineslinerrr r?s  zInputWrapper.readlinesccs |}|s dS|Vqr )r>)r4rBrrr __iter__szInputWrapper.__iter__cCtdddS)Nrz input.close() must not be calledr r4rrr closezInputWrapper.closeN) rrrr6r9r>r?rCrGrrrr r)s r)c@4eZdZddZddZddZddZd d Zd S) r*cCr2r )errors)r4 wsgi_errorsrrr r6r7zErrorWrapper.__init__cCs tt|tu|j|dSr )r rrrJwriter4srrr rLszErrorWrapper.writecCs|jdSr )rJflushrFrrr rOrHzErrorWrapper.flushcCs|D]}||qdSr )rL)r4seqrBrrr writeliness zErrorWrapper.writelinescCrD)Nrz!errors.close() must not be calledrErFrrr rGrHzErrorWrapper.closeN)rrrr6rLrOrQrGrrrr r*s  r*c@eZdZddZddZdS)rcCr2r )writer)r4Z wsgi_writerrrr r6r7zWriteWrapper.__init__cCstt|tu||dSr )r rr:rSrMrrr __call__szWriteWrapper.__call__N)rrrr6rTrrrr r rc@rR)PartialIteratorWrappercCr2r r.)r4 wsgi_iteratorrrr r6r7zPartialIteratorWrapper.__init__cCs t|jdSr )r,r.rFrrr rCs zPartialIteratorWrapper.__iter__N)rrrr6rCrrrr rVrUrVc@rI) r,cCs ||_t||_d|_||_dS)NF)original_iteratoriterr.closedcheck_start_response)r4rXr\rrr r6 s  zIteratorWrapper.__init__cCs|Sr rrFrrr rCszIteratorWrapper.__iter__cCsTt|j dt|j}t|turtdd|f|jdur(t|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)r r[nextr.rr:r\)r4r<rrr __next__s   zIteratorWrapper.__next__cCs$d|_t|jdr|jdSdS)NTrG)r[hasattrrYrGrFrrr rGs zIteratorWrapper.closecCs"|js tjdt|jddS)Nz/Iterator garbage collected without being closed)r[sysstderrrLr rFrrr __del__#szIteratorWrapper.__del__N)rrrr6rCr^rGrbrrrr r,s  r,cCstt|tudt||fdD] }t||vd|fqdD]}t||vd||ddfq d|vrr?rCz-wsgi.input (%r) doesn't have the attribute %sr r_)r5attrrrr rmk rmcCrs)N)rOrLrQz.wsgi.errors (%r) doesn't have the attribute %srt)rKrurrr rnqrvrncCszt|d}|ddd}tt|dkd|t|}t|dkd|t|dks1|dd kr;td |tdSdS) 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)rsplitr rrqrirjr)r!Z status_codeZ status_intrrr rws  rcCstt|tud|t|f|D]n}tt|tud|t|ftt|dk|\}}t|d}t|d}t|dkd|td|voKd |vd |tt|d |t| d  of| d  d|t |rtdd|t | dfqdS)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)) r rr@rlrrlower header_researchendswithbad_header_value_regroup)r"itemnamerrrr rsB        rcCst|d}t|ddd}d}|D]\}}t|d}|dkr0||vr)dStdd|q||vr>tdd|dSdS) Nrwrr)i0r|z content-typezJContent-Type header found in a %s response, which must not return content.z,No Content-Type header found in headers (%s))rrqr{rr )r!r"codeZNO_MESSAGE_BODYrrrrr rs    rcCs*t|dup t|tud|t|fdS)Nz exc_info (%r) is not a tuple: %r)r rrl)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 isinstancerr:rWrrr r+sr+)r__all__rer`ricompilerrWarningrr rrr)r*rrVr,r(rmrnrrrrr+rrrr s0j  7#  #A