�
{ fc
@ sG d Z d d l m Z d d l m Z m Z m Z d d l m Z d d l Z d d l
Z
d d l Z d d d d g Z y e
Wn e k
r� d
� Z
n Xd d d
d d d d g Z e d d d d d d d d d d d d g
Z d � Z d f d � � YZ d e f d � � YZ d e f d! � � YZ d e f d" � � YZ d S(# s/ Base classes for server/gateway implementationsi����( t
StringType( t FileWrappert guess_schemet
is_hop_by_hop( t HeadersNt BaseHandlert
SimpleHandlert BaseCGIHandlert
CGIHandlerc C s+ i } x | D] \ } } | | | 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.
N( t result_is_filet sendfileR3 t writet finish_contentR6 ( R7 t data( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR4 u s c C s
t | j � S( s Return the URL scheme being used( R R1 ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyRB � s c C sZ y t | j � } Wn t t t f k
r/ n' X| d k rV t | j � | j d Log current error, and send error output to client if possibleN( Rt t sysR^ RZ t error_outputR1 R2 R3 R4 ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR5 - s c C s' | | j | j t j � � | j g S( sZ WSGI 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!
( t error_statust
error_headersRu R^ t
error_body( R7 R1 R2 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyRv 5 s
c C s
t � d S( s Override 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( RS ( R7 RO ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyRb H s c C s
t � d S( s� 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.
N( RS ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyRf Q s c C s
t � d S( s4 Override in subclass to return suitable 'wsgi.input'N( RS ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR> Y s c C s
t � d S( s5 Override in subclass to return suitable 'wsgi.errors'N( RS ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR? ] s c C s
t � d S( s> Override in subclass to insert CGI variables in 'self.environ'N( RS ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR= a s ( i i N( s Content-Types
text/plain(6 t __name__t
__module__t __doc__R@ Rj RC RD Rg RA RG Rc RF RH R
t osR1 R R; R RE R R] Rq Rw Rx Ry R\ R3 RZ RV RU R9 R0 R4 RB RX RY R2 Rd RM RL RN R6 Re RK Ra Rt R5 Rv Rb Rf R> R? R= ( ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR * sT
c B sJ e Z d Z e e d � Z d � Z d � Z d � Z d � Z d � Z
RS( sq Handler 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)c C s: | | _ | | _ | | _ | | _ | | _ | | _ d S( N( t stdint stdoutRs t base_envRC RD ( R7 R~ R Rs R1 t multithreadt multiprocess( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyt __init__s s c C s | j S( N( R~ ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR> } s c C s | j S( N( Rs ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR? � s c C s | j j | j � d S( N( R1 t updateR� ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR= � s c C s# | j j | � | j j | _ d S( N( R RM Rb ( R7 RO ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyRb � s c C s | j j � | j j | _ d S( N( R Rr Rf ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyRf � s
( Rz R{ R| Rj Rg R� R> R? R= Rb Rf ( ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR f s c B s e Z d Z e Z RS( s� 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.
( Rz R{ R| Rg RG ( ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR � s c B s# e Z d Z e Z i Z d � Z RS( s� 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.
c
C sA t j | t j t j t j t t j j � � d t
d t �d S( NR� R� ( R R� Ru R~ R Rs R
R} R1 R Rg Rj ( R7 ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR� � s *( Rz R{ R| Rj RA R; R� ( ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyR � s ( R| t typesR t utilR R R RV R Ru R} R! t __all__R
t NameErrorR# RF R$ R/ R R R R ( ( ( s( /usr/lib64/python2.7/wsgiref/handlers.pyt s& $
� =)