File "validate.cpython-36.opt-1.pyc"

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

 
Open Edit   Advanced Editor   Back 
3


 \;;@sdZdgZddlZddlZddlZejdZejdZGdddeZ	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 zero or 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.6/wsgiref/validate.pyrysrcGs|st|dS)N)AssertionError)Zcondargsrrr	assert_~srcCs(t|tkr|Stdj|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 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 requiredzNo keyword arguments allowedcstt|dkpt|dkd|ft|d|d}|d}t|dkrV|d}nd}t|t|t||t|jdt|S)NrzInvalid number of arguments: %szNo keyword arguments allowedr)rlencheck_status
check_headerscheck_content_typecheck_exc_infoappendWriteWrapper)rkwstatusheadersexc_info)start_responsestart_response_startedrr	start_response_wrappers


z;validator.<locals>.lint_app.<locals>.start_response_wrapperz
wsgi.inputzwsgi.errorsFz>The application must return an iterator, if only an empty list)rr
check_environInputWrapperErrorWrappercheck_iteratorIteratorWrapper)rrenvironr$iterator)application)r"r#r	lint_apps
zvalidator.<locals>.lint_appr)r,r-r)r,r	rs)c@s<eZdZddZddZddZddZd	d
ZddZd
S)r&cCs
||_dS)N)input)self
wsgi_inputrrr	__init__szInputWrapper.__init__cGs0tt|dk|jj|}tt|tk|S)Nr)rrr.readr
bytes)r/rvrrr	r2szInputWrapper.readcGs0tt|dk|jj|}tt|tk|S)Nr)rrr.readliner
r3)r/rr4rrr	r5szInputWrapper.readlinecGsNtt|dk|jj|}tt|tkx|D]}tt|tkq2W|S)Nr)rrr.	readlinesr
listr3)r/rlineslinerrr	r6s
zInputWrapper.readlinesccs x|j}|sdS|VqWdS)N)r5)r/r9rrr	__iter__s
zInputWrapper.__iter__cCstdddS)Nrz input.close() must not be called)r)r/rrr	closeszInputWrapper.closeN)	rrrr1r2r5r6r:r;rrrr	r&sr&c@s4eZdZddZddZddZddZd	d
ZdS)r'cCs
||_dS)N)errors)r/wsgi_errorsrrr	r1szErrorWrapper.__init__cCs tt|tk|jj|dS)N)rr
rr<write)r/srrr	r>szErrorWrapper.writecCs|jjdS)N)r<flush)r/rrr	r@szErrorWrapper.flushcCsx|D]}|j|qWdS)N)r>)r/seqr9rrr	
writeliness
zErrorWrapper.writelinescCstdddS)Nrz!errors.close() must not be called)r)r/rrr	r;szErrorWrapper.closeN)rrrr1r>r@rBr;rrrr	r's
r'c@seZdZddZddZdS)rcCs
||_dS)N)writer)r/Zwsgi_writerrrr	r1szWriteWrapper.__init__cCstt|tk|j|dS)N)rr
r3rC)r/r?rrr	__call__szWriteWrapper.__call__N)rrrr1rDrrrr	rsrc@seZdZddZddZdS)PartialIteratorWrappercCs
||_dS)N)r+)r/
wsgi_iteratorrrr	r1szPartialIteratorWrapper.__init__cCst|jdS)N)r)r+)r/rrr	r:szPartialIteratorWrapper.__iter__N)rrrr1r:rrrr	rEsrEc@s4eZdZddZddZddZddZd	d
ZdS)r)cCs ||_t||_d|_||_dS)NF)original_iteratoriterr+closedcheck_start_response)r/rFrJrrr	r1	s
zIteratorWrapper.__init__cCs|S)Nr)r/rrr	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rInextr+r
r3rJ)r/r4rrr	__next__s

zIteratorWrapper.__next__cCs d|_t|jdr|jjdS)NTr;)rIhasattrrGr;)r/rrr	r;szIteratorWrapper.closecCs"|jstjjdt|jddS)Nz/Iterator garbage collected without being closed)rIsysstderrr>r)r/rrr	__del__#s
zIteratorWrapper.__del__N)rrrr1r:rLr;rPrrrr	r)s
r)c	Cstt|tkdt||fx d,D]}t||kd|fq$Wx*d-D]"}t||kd||ddfqFWd|krtjdtxF|jD]:}d|krqtt||tkd|t||||fqWtt|dtkd|dft|dd.kd|dt	|dt
|d|dd/kr<tjd!|dtt|jd"pX|d"jd#d$|d"t|jd%p|d%jd#d&|d%|jd'rtt
|d'd(kd)|d'|jd"std%|kd*t|jd"d#kd+dS)0Nz:Environment is not of the right type: %r (environment: %r)REQUEST_METHODSERVER_NAMESERVER_PORTwsgi.version
wsgi.inputwsgi.errorswsgi.multithreadwsgi.multiprocess
wsgi.run_oncez$Environment missing required key: %rHTTP_CONTENT_TYPEHTTP_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)z#wsgi.version should be a tuple (%r)zwsgi.url_schemehttphttpszwsgi.url_scheme unknown: %rGETHEADPOSTOPTIONSPATCHPUTDELETETRACEzUnknown 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 '/')	rQrRrSrTrUrVrWrXrY)rZr[)r^r_)r`rarbrcrdrerfrg)rr
dictwarningswarnrkeysrtuplecheck_inputcheck_errorsget
startswithint)r*keyrrr	r%*s`

r%cCs*x$dD]}tt||d||fqWdS)Nr2r5r6r:z-wsgi.input (%r) doesn't have the attribute %s)r2r5r6r:)rrM)r0attrrrr	rnks

rncCs*x$dD]}tt||d||fqWdS)Nr@r>rBz.wsgi.errors (%r) doesn't have the attribute %s)r@r>rB)rrM)r=rtrrr	roqs

rocCsvt|d}|jddd}tt|dkd|t|}t|dkd|t|dksb|dd	krrtjd
|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rrrrjrkr)rZstatus_codeZ
status_intrrr	rws

rcCstt|tkd|t|fi}x|D]}tt|tkd|t|ftt|dk|\}}t|d}t|d}t|jdkd|d||j<td|kod	|kd
|ttj|d|t|j	do|j	d
d|t
j|r(tdd|t
j|jdfq(WdS)Nz%Headers (%r) must be of type list: %rz1Individual headers (%r) must be of type tuple: %rrzHeader namezHeader valuerzyThe 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r
r7rmrrlower	header_researchendswithbad_header_value_regroup)r Zheader_namesitemnamerrrr	rs0





rcCs~t|d}t|jddd}d
}x@|D]8\}}t|d}|jdkr(||krRdStdd|q(W||krztdd	|dS)Nrurr0zHeader namezcontent-typezJContent-Type header found in a %s response, which must not return content.z,No Content-Type header found in headers (%s))rr)rrrryr~r)rr codeZNO_MESSAGE_BODYrrrrr	rs

rcCs*t|dkpt|tkd|t|fdS)Nz exc_info (%r) is not a tuple: %r)rr
rm)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
isinstancerr3)r+rrr	r(sr()r__all__rerNrjcompilerrWarningrrrrr&r'rrEr)r%rnrorrrrr(rrrr	<module>ns.

7#		#A