File "validate.cpython-38.pyc"

Full Path: /home/attunedd/public_html/byp/izo/con7ext_sym404/rintoar.txt/lib64/python3.8/wsgiref/__pycache__/validate.cpython-38.pyc
File size: 14.41 KB
MIME-type: text/x-bytecode.python
Charset: 8 bit

 
Open Edit   Advanced Editor   Back 
U

e5d:@sdZdgZddlZddlZddlZedZedZGdddeZ	dd	Z
d
dZd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__rr(/usr/lib64/python3.8/wsgiref/validate.pyrysrcGs|st|dSN)AssertionError)Zcondargsrrr	assert_~sr
cCs(t|tkr|Std|t|dS)Nz!{0} must be of type str (got {1}))typestrrformatrepr)valuetitlerrr	check_string_types
rcsfdd}|S)a
    When applied between a WSGI server and a WSGI application, this
    middleware will check for WSGI compliancy 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|dk	oz|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)r
lencheck_status
check_headerscheck_content_typecheck_exc_infoappendWriteWrapper)rkwstatusheadersexc_infoZstart_responseZstart_response_startedrr	start_response_wrappers


z;validator.<locals>.lint_app.<locals>.start_response_wrapper
wsgi.inputwsgi.errorsFz>The application must return an iterator, if only an empty list)r
r
check_environInputWrapperErrorWrappercheck_iteratorIteratorWrapper)rr environr%iteratorapplicationr$r	lint_apps
zvalidator.<locals>.lint_appr)r0r1rr/r	rs)c@s<eZdZddZddZddZddZd	d
ZddZd
S)r)cCs
||_dSr
)input)self
wsgi_inputrrr	__init__szInputWrapper.__init__cGs0tt|dk|jj|}tt|tk|SNr)r
rr2readrbytesr3rvrrr	r7szInputWrapper.readcGs0tt|dk|jj|}tt|tk|Sr6)r
rr2readlinerr8r9rrr	r;szInputWrapper.readlinecGsJtt|dk|jj|}tt|tk|D]}tt|tkq0|Sr6)r
rr2	readlinesrlistr8)r3rlineslinerrr	r<szInputWrapper.readlinesccs|}|sdS|VqdSr
)r;)r3r?rrr	__iter__szInputWrapper.__iter__cCstdddS)Nrz input.close() must not be calledr
r3rrr	closeszInputWrapper.closeN)	rrrr5r7r;r<r@rCrrrr	r)sr)c@s4eZdZddZddZddZddZd	d
ZdS)r*cCs
||_dSr
)errors)r3wsgi_errorsrrr	r5szErrorWrapper.__init__cCs tt|tk|j|dSr
)r
rrrDwriter3srrr	rFszErrorWrapper.writecCs|jdSr
)rDflushrBrrr	rIszErrorWrapper.flushcCs|D]}||qdSr
)rF)r3seqr?rrr	
writelinesszErrorWrapper.writelinescCstdddS)Nrz!errors.close() must not be calledrArBrrr	rCszErrorWrapper.closeN)rrrr5rFrIrKrCrrrr	r*s
r*c@seZdZddZddZdS)rcCs
||_dSr
)writer)r3Zwsgi_writerrrr	r5szWriteWrapper.__init__cCstt|tk||dSr
)r
rr8rLrGrrr	__call__szWriteWrapper.__call__N)rrrr5rMrrrr	rsrc@seZdZddZddZdS)PartialIteratorWrappercCs
||_dSr
r.)r3
wsgi_iteratorrrr	r5szPartialIteratorWrapper.__init__cCst|jdSr
)r,r.rBrrr	r@szPartialIteratorWrapper.__iter__N)rrrr5r@rrrr	rNsrNc@s4eZdZddZddZddZddZd	d
ZdS)r,cCs ||_t||_d|_||_dS)NF)original_iteratoriterr.closedcheck_start_response)r3rPrTrrr	r5	s
zIteratorWrapper.__init__cCs|Sr
rrBrrr	r@szIteratorWrapper.__iter__cCsTt|jdt|j}t|tk	r4tdd|f|jdk	rPt|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
rSnextr.rr8rT)r3r:rrr	__next__s

zIteratorWrapper.__next__cCs d|_t|jdr|jdS)NTrC)rShasattrrQrCrBrrr	rCszIteratorWrapper.closecCs"|jstjdt|jddS)Nz/Iterator garbage collected without being closed)rSsysstderrrFr
rBrrr	__del__#szIteratorWrapper.__del__N)rrrr5r@rVrCrZrrrr	r,s
r,cCstt|tkdt||fdD]}t||kd|fq"dD]"}t||kd||ddfq@d|krxtdt|D]:}d	|krqtt||tkd
|t||||fqtt|dtkd|dft|d
dkd|d
t	|dt
|d|ddkr0td|dtt|dpL|ddd|dt|dpv|ddd|d|drtt
|ddkd|d|dstd|kdt|ddkddS)Nz:Environment is not of the right type: %r (environment: %r))	REQUEST_METHODZSERVER_NAMEZSERVER_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)ZhttpZhttpszwsgi.url_scheme unknown: %rr&r'r[)ZGETZHEADZPOSTZOPTIONSZPATCHZPUTZDELETEZTRACEzUnknown REQUEST_METHOD: %rZSCRIPT_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 '/')r
rdictwarningswarnrkeysrtuplecheck_inputcheck_errorsget
startswithint)r-keyrrr	r(*sx





r(cCs&dD]}tt||d||fqdS)N)r7r;r<r@z-wsgi.input (%r) doesn't have the attribute %sr
rW)r4attrrrr	reks
recCs&dD]}tt||d||fqdS)N)rIrFrKz.wsgi.errors (%r) doesn't have the attribute %srk)rErlrrr	rfqs
rfcCsvt|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)rsplitr
rrirarbr)r!Zstatus_codeZ
status_intrrr	rws
rcCstt|tkd|t|f|D]}tt|tkd|t|ftt|dk|\}}t|d}t|d}t|dkd|td|kod	|kd
|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: %rrHeader 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=rdrrlower	header_researchendswithbad_header_value_regroup)r"itemnamerrrr	rs>




rcCs|t|d}t|ddd}d}|D]:\}}t|d}|dkr&||krRdStdd|q&||krxtdd|dS)	Nrmrr)i0rrzcontent-typezJContent-Type header found in a %s response, which must not return content.z,No Content-Type header found in headers (%s))rrirqrwr
)r!r"codeZNO_MESSAGE_BODYr~rrrr	rs

rcCs*t|dkpt|tkd|t|fdS)Nz exc_info (%r) is not a tuple: %r)r
rrd)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

isinstancerr8rOrrr	r+sr+)r__all__rerXracompilerxr{Warningrr
rrr)r*rrNr,r(rerfrrrrr+rrrr	<module>s.j

7#		#A