Tryag File Manager
Home
-
Turbo Force
Current Path :
/
usr
/
lib
/
python2.4
/
Upload File :
New :
File
Dir
//usr/lib/python2.4/BaseHTTPServer.pyo
m =5Dc @ s d Z d Z d d g Z d k Z d k Z d k Z d k Z d k Z d Z d Z d e i f d YZ d e i f d YZ e e d d Z e d j o e n d S( s HTTP server base class. Note: the class in this module doesn't implement any HTTP request; see SimpleHTTPServer for simple implementations of GET, HEAD and POST (including CGI scripts). It does, however, optionally implement HTTP/1.1 persistent connections, as of version 0.3. Contents: - BaseHTTPRequestHandler: HTTP request handler base class - test: test function XXX To do: - log requests even later (to capture byte count) - log user-agent header and other interesting goodies - send error log to separate file s 0.3t HTTPServert BaseHTTPRequestHandlerNs <head> <title>Error response</title> </head> <body> <h1>Error response</h1> <p>Error code %(code)d. <p>Message: %(message)s. <p>Error code explanation: %(code)s = %(explain)s. </body> c C s( | i d d i d d i d d S( Nt &s &t <s <t >s >( t htmlt replace( R ( ( t$ /usr/lib/python2.4/BaseHTTPServer.pyt _quote_html\ s c B s t Z d Z d Z RS( Ni c C sH t i i | | i i d \ } } t i | | _ | | _ d S( s. Override server_bind to store the server name.i N( t SocketServert TCPServert server_bindt selft sockett getsocknamet hostt portt getfqdnt server_namet server_port( R R R ( ( R R c s ( t __name__t __module__t allow_reuse_addressR ( ( ( R R _ s c B s t Z d Z d e i i d Z d e Z d Z d Z d Z e d Z e Z e d Z d Z d Z d d d Z d Z d Z d Z d Z d Z d 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& Z e i Z h d' d <d* d <d- d <d0 d <d3 d <d6 d <d9 d <d< d <d? d <dB d <dE d <dH d <dK d <dN d <dQ d <dT d <dV d <dY d <d\ d <d_ d <db d <de d <dh d <dk d <dn d <dq d <dt d <dw d <dz d <d} d <d d <d d <d d <d d <d d <d d <d d <d d <d d <d d <Z RS( s HTTP request handler base class. The following explanation of HTTP serves to guide you through the code as well as to expose any misunderstandings I may have about HTTP (so you don't need to read the code to figure out I'm wrong :-). HTTP (HyperText Transfer Protocol) is an extensible protocol on top of a reliable stream transport (e.g. TCP/IP). The protocol recognizes three parts to a request: 1. One line identifying the request type and path 2. An optional set of RFC-822-style headers 3. An optional data part The headers and data are separated by a blank line. The first line of the request has the form <command> <path> <version> where <command> is a (case-sensitive) keyword such as GET or POST, <path> is a string containing path information for the request, and <version> should be the string "HTTP/1.0" or "HTTP/1.1". <path> is encoded using the URL encoding scheme (using %xx to signify the ASCII character with hex code xx). The specification specifies that lines are separated by CRLF but for compatibility with the widest range of clients recommends servers also handle LF. Similarly, whitespace in the request line is treated sensibly (allowing multiple spaces between components and allowing trailing whitespace). Similarly, for output, lines ought to be separated by CRLF pairs but most clients grok LF characters just fine. If the first line of the request has the form <command> <path> (i.e. <version> is left out) then this is assumed to be an HTTP 0.9 request; this form has no optional headers and data part and the reply consists of just the data. The reply form of the HTTP 1.x protocol again has three parts: 1. One line giving the response code 2. An optional set of RFC-822-style headers 3. The data Again, the headers and data are separated by a blank line. The response code line has the form <version> <responsecode> <responsestring> where <version> is the protocol version ("HTTP/1.0" or "HTTP/1.1"), <responsecode> is a 3-digit response code indicating success or failure of the request, and <responsestring> is an optional human-readable string explaining what the response code means. This server parses the request and the headers, and then calls a function specific to the request type (<command>). Specifically, a request SPAM will be handled by a method do_SPAM(). If no such method exists the server sends an error response to the client. If it exists, it is called with no arguments: do_SPAM() Note that the request name is case sensitive (i.e. SPAM and spam are different requests). The various request details are stored in instance variables: - client_address is the client IP address in the form (host, port); - command, path and version are the broken-down request line; - headers is an instance of mimetools.Message (or a derived class) containing the header information; - rfile is a file object open for reading positioned at the start of the optional input data part; - wfile is a file object open for writing. IT IS IMPORTANT TO ADHERE TO THE PROTOCOL FOR WRITING! The first thing to be written must be the response line. Then follow 0 or more header lines, then a blank line, and then the actual data (if any). The meaning of the header lines depends on the command executed by the server; in most cases, when data is returned, there should be at least one header line of the form Content-type: <type>/<subtype> where <type> and <subtype> should be registered MIME types, e.g. "text/html" or "text/plain". s Python/i s BaseHTTP/c C s d | _ d | _ } d | _ | i } | d d j o | d } n | d d j o | d } n | | _ | i } t | d j o-| \ } } } | d d j o | i d d | t Sn yf | i d d d } | i d } t | d j o t n t | d t | d f } Wn1 t t f j o | i d d | t Sn X| d j o | i d j o d | _ n | d j o | i d d | t Sq7n} t | d j oB | \ } } d | _ | d j o | i d d | t Sq7n( | p t Sn | i d d | t S| | | | _ | _ | _ | i | i d | _ | i i d d } | i d j o d | _ n1 | i d j o | i d j o d | _ n t S( s' Parse a request (internal). The request should be stored in self.raw_requestline; the results are in self.command, self.path, self.request_version and self.headers. Return True for success, False for failure; on failure, an error is sent back. s HTTP/0.9i is is i i s HTTP/i s Bad request version (%r)t /t .i i s HTTP/1.1i s Invalid HTTP Version (%s)t GETs Bad HTTP/0.9 request type (%r)s Bad request syntax (%r)t Connectiont t closes keep-aliveN( i i ( i i ( t NoneR t commandt request_versiont versiont close_connectiont raw_requestlinet requestlinet splitt wordst lent patht send_errort Falset base_version_numbert version_numbert ValueErrort intt IndexErrort protocol_versiont MessageClasst rfilet headerst gett conntypet lowert True( R R# R* R4 R R R% R' R+ ( ( R t parse_request sd $ # c C s | i i | _ | i p d | _ d Sn | i p d Sn d | i } t | | p | i d d | i d Sn t | | } | d S( s Handle a single HTTP request. You normally don't need to override this method; see the class __doc__ string for information on how to handle specific HTTP commands such as GET and POST. i Nt do_i s Unsupported method (%r)( R R1 t readlineR" R! R7 R t mnamet hasattrR( t getattrt method( R R: R= ( ( R t handle_one_request# s c C s3 d | _ | i x | i p | i q Wd S( s& Handle multiple requests if necessary.i N( R R! R> ( R ( ( R t handle8 s c C s y | i | \ } } Wn t j o d \ } } n X| d j o | } n | } | i d | | | i h d | <d t | <d | <} | i | | | i d d | i d d | i | i d j o. | d j o! | d j o | i i | n d S( s Send and log an error reply. Arguments are the error code, and a detailed message. The detailed message defaults to the short entry matching the response code. This sends an error response (so it must be called before any output has been generated), logs the error, and finally sends a piece of HTML explaining the error to the user. s ???s code %d, message %st codet messaget explains Content-Types text/htmlR R t HEADi i i0 N( s ???s ???( i i0 ( R t responsesR@ t shortt longt KeyErrorRA R RB t log_errort error_message_formatR t contentt send_responset send_headert end_headersR t wfilet write( R R@ RA RF RJ RE RB ( ( R R( @ s . *c C s | i | | d j o/ | | i j o | i | d } qI d } n | i d j o$ | i i d | i | | f n | i d | i | i d | i d S( s Send the response header and log the response code. Also send two standard headers with the server software version and the current date. i R s HTTP/0.9s %s %d %s t Servert DateN( R t log_requestR@ RA R RD R RN RO R/ RL t version_stringt date_time_string( R R@ RA ( ( R RK a s $c C s | i d j o | i i d | | f n | i d j oD | i d j o d | _ q | i d j o d | _ q n d S( s Send a MIME header.s HTTP/0.9s %s: %s t connectionR i s keep-alivei N( R R RN RO t keywordt valueR5 R! ( R RV RW ( ( R RL u s c C s( | i d j o | i i d n d S( s, Send the blank line ending the MIME headers.s HTTP/0.9s N( R R RN RO ( R ( ( R RM s t -c C s) | i d | i t | t | d S( sN Log an accepted request. This is called by send_response(). s "%s" %s %sN( R t log_messageR# t strR@ t size( R R@ R[ ( ( R RR s c G s | i | d S( s Log an error. This is called when a request cannot be fulfilled. By default it passes the message on to log_message(). Arguments are the same as for log_message(). XXX This should go to the separate error log. N( R RY t args( R R\ ( ( R RH s c G s1 t i i d | i | i | | f d S( s Log an arbitrary message. This is used by all other logging functions. Override it if you have specific logging wishes. The first argument, FORMAT, is a format string for the message to be logged. If the format string contains any % escapes requiring parameters, they should be specified as subsequent arguments (it's just like printf!). The client host and current date/time are prefixed to every message. s %s - - [%s] %s N( t syst stderrRO R t address_stringt log_date_time_stringt formatR\ ( R Ra R\ ( ( R RY s c C s | i d | i S( s* Return the server software version string.t N( R t server_versiont sys_version( R ( ( R RS s c C sg t i } t i | \ } } } } } } } } } d | i | | | i | | | | | f } | S( s@ Return the current date and time formatted for a message header.s# %s, %02d %3s %4d %02d:%02d:%02d GMTN( t timet nowt gmtimet yeart montht dayt hht mmt sst wdt yt zR t weekdaynamet monthnamet s( R Rn Rl Rs Ri Rm Rk Rp Rh Ro Rf Rj ( ( R RT s *-c C s] t i } t i | \ } } } } } } } } } d | | i | | | | | f } | S( s. Return the current time formatted for logging.s %02d/%3s/%04d %02d:%02d:%02dN( Re Rf t localtimeRh Ri Rj Rk Rl Rm t xRo Rp R Rr Rs ( R Rp Rl Rs Ri Rm Rk Rh Ro Ru Rf Rj ( ( R R` s *#t Mont Tuet Wedt Thut Frit Satt Sunt Jant Febt Mart Aprt Mayt Junt Jult Augt Sept Octt Novt Decc C s | i d \ } } t i | S( s Return the client address formatted for logging. This version looks up the full hostname using gethostbyaddr(), and tries to find a name that contains at least one dot. i N( R t client_addressR R R R ( R R R ( ( R R_ s s HTTP/1.0id t Continues! Request received, please continueie s Switching Protocolss. Switching to new protocol; obey Upgrade headeri t OKs# Request fulfilled, document followsi t Createds Document created, URL followsi t Accepteds/ Request accepted, processing continues off-linei s Non-Authoritative Informations Request fulfilled from cachei s No responses" Request fulfilled, nothing followsi s Reset Contents# Clear input form for further input.i s Partial Contents Partial content follows.i, s Multiple Choicess, Object has several resources -- see URI listi- s Moved Permanentlys( Object moved permanently -- see URI listi. t Founds( Object moved temporarily -- see URI listi/ s See Others' Object moved -- see Method and URL listi0 s Not modifieds) Document has not changed since given timei1 s Use ProxysA You must use proxy specified in Location to access this resource.i3 s Temporary Redirecti s Bad requests( Bad request syntax or unsupported methodi t Unauthorizeds* No permission -- see authorization schemesi s Payment requireds" No payment -- see charging schemesi t Forbiddens0 Request forbidden -- authorization will not helpi s Not Founds Nothing matches the given URIi s Method Not Alloweds, Specified method is invalid for this server.i s Not Acceptables& URI not available in preferred format.i s Proxy Authentication Requireds8 You must authenticate with this proxy before proceeding.i s Request Time-outs# Request timed out; try again later.i t Conflicts Request conflict.i t Gones6 URI no longer exists and has been permanently removed.i s Length Requireds# Client must specify Content-Length.i s Precondition Faileds! Precondition in headers is false.i s Request Entity Too Larges Entity is too large.i s Request-URI Too Longs URI is too long.i s Unsupported Media Types" Entity body in unsupported format.i s Requested Range Not Satisfiables Cannot satisfy request range.i s Expectation Faileds( Expect condition could not be satisfied.i s Internal errors Server got itself in troublei s Not Implementeds& Server does not support this operationi s Bad Gateways, Invalid responses from another server/proxy.i s Service temporarily overloadeds8 The server cannot process the request due to a high loadi s Gateway timeouts4 The gateway server did not receive a timely responsei s HTTP Version not supporteds Cannot fulfill request.( R s! Request received, please continue( s Switching Protocolss. Switching to new protocol; obey Upgrade header( R s# Request fulfilled, document follows( R s Document created, URL follows( R s/ Request accepted, processing continues off-line( s Non-Authoritative Informations Request fulfilled from cache( s No responses" Request fulfilled, nothing follows( s Reset Contents# Clear input form for further input.( s Partial Contents Partial content follows.( s Multiple Choicess, Object has several resources -- see URI list( s Moved Permanentlys( Object moved permanently -- see URI list( R s( Object moved temporarily -- see URI list( s See Others' Object moved -- see Method and URL list( s Not modifieds) Document has not changed since given time( s Use ProxysA You must use proxy specified in Location to access this resource.( s Temporary Redirects( Object moved temporarily -- see URI list( s Bad requests( Bad request syntax or unsupported method( R s* No permission -- see authorization schemes( s Payment requireds" No payment -- see charging schemes( R s0 Request forbidden -- authorization will not help( s Not Founds Nothing matches the given URI( s Method Not Alloweds, Specified method is invalid for this server.( s Not Acceptables& URI not available in preferred format.( s Proxy Authentication Requireds8 You must authenticate with this proxy before proceeding.( s Request Time-outs# Request timed out; try again later.( R s Request conflict.( R s6 URI no longer exists and has been permanently removed.( s Length Requireds# Client must specify Content-Length.( s Precondition Faileds! Precondition in headers is false.( s Request Entity Too Larges Entity is too large.( s Request-URI Too Longs URI is too long.( s Unsupported Media Types" Entity body in unsupported format.( s Requested Range Not Satisfiables Cannot satisfy request range.( s Expectation Faileds( Expect condition could not be satisfied.( s Internal errors Server got itself in trouble( s Not Implementeds& Server does not support this operation( s Bad Gateways, Invalid responses from another server/proxy.( s Service temporarily overloadeds8 The server cannot process the request due to a high load( s Gateway timeouts4 The gateway server did not receive a timely response( s HTTP Version not supporteds Cannot fulfill request.(! R R t __doc__R] R R$ Rd t __version__Rc R7 R> R? R R( t DEFAULT_ERROR_MESSAGERI RK RL RM RR RH RY RS RT R` Rq Rr R_ R/ t mimetoolst MessageR0 RD ( ( ( R R k s. f H - s HTTP/1.0c C s t i d o t t i d } n d } d | f } | | _ | | | } | i i } d G| d Gd G| d Gd GH| i d S( s Test the HTTP request handler class. This runs an HTTP server on port 8000 (or the first command line argument). i i@ R s Serving HTTP oni R s ...N( R] t argvR- R t server_addresst protocolt HandlerClassR/ t ServerClasst httpdR R t sat serve_forever( R R R R R R R ( ( R t test) s t __main__( R R t __all__R] Re R R R R R R R t StreamRequestHandlerR R R ( R R R R R R R] R Re R R R ( ( R t ? s 3