ok
Direktori : /proc/self/root/proc/self/root/lib64/python3.6/http/__pycache__/ |
Current File : //proc/self/root/proc/self/root/lib64/python3.6/http/__pycache__/server.cpython-36.pyc |
3 \� � @ s� d Z dZddddgZddlZddlZddlZddlZddl Z ddl Z ddlZddlZddl Z ddlZddlZddlZddlZddlZddlZddlZddlmZ d Zd ZG dd� dej�ZG dd� dej�ZG d d� de�Zdd� Zdadd� Z dd� Z!G dd� de�Z"eedddfdd�Z#e$dk�r�ej%� Z&e&j'dddd� e&j'dd dd!d"d#� e&j'd$d%de(d&d'd(� e&j)� Z*e*j+�r~e"Z,neZ,e#e,e*j-e*j.d)� dS )*a@ HTTP server classes. Note: BaseHTTPRequestHandler doesn't implement any HTTP request; see SimpleHTTPRequestHandler for simple implementations of GET, HEAD and POST, and CGIHTTPRequestHandler for CGI scripts. It does, however, optionally implement HTTP/1.1 persistent connections, as of version 0.3. Notes on CGIHTTPRequestHandler ------------------------------ This class implements GET and POST requests to cgi-bin scripts. If the os.fork() function is not present (e.g. on Windows), subprocess.Popen() is used as a fallback, with slightly altered semantics. In all cases, the implementation is intentionally naive -- all requests are executed synchronously. SECURITY WARNING: DON'T USE THIS CODE UNLESS YOU ARE INSIDE A FIREWALL -- it may execute arbitrary Python code or external programs. Note that status code 200 is sent prior to execution of a CGI script, so scripts cannot send other status codes such as 302 (redirect). 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 z0.6� HTTPServer�BaseHTTPRequestHandler�SimpleHTTPRequestHandler�CGIHTTPRequestHandler� N)� HTTPStatusa� <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"> <title>Error response</title> </head> <body> <h1>Error response</h1> <p>Error code: %(code)d</p> <p>Message: %(message)s.</p> <p>Error code explanation: %(code)s - %(explain)s.</p> </body> </html> ztext/html;charset=utf-8c @ s e Zd ZdZdd� ZdS )r � c C s4 t jj| � | jdd� \}}tj|�| _|| _dS )z.Override server_bind to store the server name.N� )�socketserver� TCPServer�server_bind�server_address�socketZgetfqdn�server_name�server_port)�self�host�port� r �/usr/lib64/python3.6/server.pyr � s zHTTPServer.server_bindN)�__name__� __module__�__qualname__Zallow_reuse_addressr r r r r r � s c @ s e Zd ZdZdejj� d Zde Z e ZeZ dZdd� Zdd � Zd d� Zdd � Zd@dd�ZdAdd�ZdBdd�Zdd� Zdd� Zdd� ZdCdd�Zdd� Zd d!� Zd"d#� ZdDd$d%�Zd&d'� Zd(d)d*d+d,d-d.gZdd/d0d1d2d3d4d5d6d7d8d9d:g Z d;d<� Z!d=Z"e#j$j%Z&d>d?� e'j(j)� D �Z*dS )Er a� 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 email.message.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". zPython/r z BaseHTTP/zHTTP/0.9c C s� d| _ | j | _}d| _t| jd�}|jd�}|| _|j� }t |�dk�r|\}}}yZ|dd� dkrjt �|jdd �d }|jd �}t |�dkr�t �t|d �t|d �f}W n* t tfk r� | j tjd | � dS X |dkr�| jdkr�d| _|dk�rr| j tjd| � dS n^t |�dk�rR|\}}d| _|dk�rr| j tjd| � dS n |�s\dS | j tjd| � dS ||| | _ | _| _ytjj| j| jd�| _W nr tjjk �r� } z| j tjdt|�� dS d}~X n: tjjk �r } z| j tjdt|�� dS d}~X nX | jjdd�} | j� dk�r:d| _n | j� dk�rZ| jdk�rZd| _| jjdd�} | j� dk�r�| jdk�r�| jdk�r�| j� �s�dS dS )a' 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. NTz iso-8859-1z � � zHTTP/�/r �.r r zBad request version (%r)FzHTTP/1.1zInvalid HTTP version (%s)ZGETzBad HTTP/0.9 request type (%r)zBad request syntax (%r))Z_classz Line too longzToo many headers� Connection� �closez keep-aliveZExpectz100-continue)r r )r r )�command�default_request_version�request_version�close_connection�str�raw_requestline�rstrip�requestline�split�len� ValueError�int� IndexError� send_errorr ZBAD_REQUEST�protocol_versionZHTTP_VERSION_NOT_SUPPORTED�path�http�clientZ parse_headers�rfile�MessageClass�headersZLineTooLongZREQUEST_HEADER_FIELDS_TOO_LARGEZ HTTPException�get�lower�handle_expect_100)r �versionr&