http.server — HTTP servers¶
Source code:Lib/http/server.py
This module defines classes for implementing HTTP servers.
Warning
http.server is not recommended for production. It only implementsbasic security checks.
Availability: not WASI.
This module does not work or is not available on WebAssembly. SeeWebAssembly platforms for more information.
One class,HTTPServer, is asocketserver.TCPServer subclass.It creates and listens at the HTTP socket, dispatching the requests to ahandler. Code to create and run the server looks like this:
defrun(server_class=HTTPServer,handler_class=BaseHTTPRequestHandler):server_address=('',8000)httpd=server_class(server_address,handler_class)httpd.serve_forever()
- classhttp.server.HTTPServer(server_address,RequestHandlerClass)¶
This class builds on the
TCPServerclass by storingthe server address as instance variables namedserver_nameandserver_port. The server is accessible by the handler, typicallythrough the handler’sserverinstance variable.
- classhttp.server.ThreadingHTTPServer(server_address,RequestHandlerClass)¶
This class is identical to HTTPServer but uses threads to handlerequests by using the
ThreadingMixIn. Thisis useful to handle web browsers pre-opening sockets, on whichHTTPServerwould wait indefinitely.Added in version 3.7.
- classhttp.server.HTTPSServer(server_address,RequestHandlerClass,bind_and_activate=True,*,certfile,keyfile=None,password=None,alpn_protocols=None)¶
Subclass of
HTTPServerwith a wrapped socket using thesslmodule.If thesslmodule is not available, instantiating aHTTPSServerobject fails with aRuntimeError.Thecertfile argument is the path to the SSL certificate chain file,and thekeyfile is the path to file containing the private key.
Apassword can be specified for files protected and wrapped with PKCS#8,but beware that this could possibly expose hardcoded passwords in clear.
See also
See
ssl.SSLContext.load_cert_chain()for additionalinformation on the accepted values forcertfile,keyfileandpassword.When specified, thealpn_protocols argument must be a sequence of stringsspecifying the “Application-Layer Protocol Negotiation” (ALPN) protocolssupported by the server. ALPN allows the server and the client to negotiatethe application protocol during the TLS handshake.
By default, it is set to
["http/1.1"], meaning the server supports HTTP/1.1.Added in version 3.14.
- classhttp.server.ThreadingHTTPSServer(server_address,RequestHandlerClass,bind_and_activate=True,*,certfile,keyfile=None,password=None,alpn_protocols=None)¶
This class is identical to
HTTPSServerbut uses threads to handlerequests by inheriting fromThreadingMixIn. This isanalogous toThreadingHTTPServeronly usingHTTPSServer.Added in version 3.14.
TheHTTPServer,ThreadingHTTPServer,HTTPSServer andThreadingHTTPSServer must be given aRequestHandlerClass oninstantiation, of which this module provides three different variants:
- classhttp.server.BaseHTTPRequestHandler(request,client_address,server)¶
This class is used to handle the HTTP requests that arrive at the server. Byitself, it cannot respond to any actual HTTP requests; it must be subclassedto handle each request method (e.g. GET or POST).
BaseHTTPRequestHandlerprovides a number of class and instancevariables, and methods for use by subclasses.The handler will parse the request and the headers, then call a methodspecific to the request type. The method name is constructed from therequest. For example, for the request method
SPAM, thedo_SPAM()method will be called with no arguments. All of the relevant information isstored in instance variables of the handler. Subclasses should not need tooverride or extend the__init__()method.BaseHTTPRequestHandlerhas the following instance variables:- client_address¶
Contains a tuple of the form
(host,port)referring to the client’saddress.
- server¶
Contains the server instance.
- close_connection¶
Boolean that should be set before
handle_one_request()returns,indicating if another request may be expected, or if the connection shouldbe shut down.
- requestline¶
Contains the string representation of the HTTP request line. Theterminating CRLF is stripped. This attribute should be set by
handle_one_request(). If no valid request line was processed, itshould be set to the empty string.
- command¶
Contains the command (request type). For example,
'GET'.
- path¶
Contains the request path. If query component of the URL is present,then
pathincludes the query. Using the terminology ofRFC 3986,pathhere includeshier-partand thequery.
- request_version¶
Contains the version string from the request. For example,
'HTTP/1.0'.
- headers¶
Holds an instance of the class specified by the
MessageClassclassvariable. This instance parses and manages the headers in the HTTPrequest. Theparse_headers()function fromhttp.clientis used to parse the headers and it requires that theHTTP request provide a validRFC 5322 style header.
- rfile¶
An
io.BufferedIOBaseinput stream, ready to read fromthe start of the optional input data.
- wfile¶
Contains the output stream for writing a response back to theclient. Proper adherence to the HTTP protocol must be used when writing tothis stream in order to achieve successful interoperation with HTTPclients.
Changed in version 3.6:This is an
io.BufferedIOBasestream.
BaseHTTPRequestHandlerhas the following attributes:- server_version¶
Specifies the server software version. You may want to override this. Theformat is multiple whitespace-separated strings, where each string is ofthe form name[/version]. For example,
'BaseHTTP/0.2'.
- sys_version¶
Contains the Python system version, in a form usable by the
version_stringmethod and theserver_versionclassvariable. For example,'Python/1.4'.
- error_message_format¶
Specifies a format string that should be used by
send_error()methodfor building an error response to the client. The string is filled bydefault with variables fromresponsesbased on the status codethat passed tosend_error().
- error_content_type¶
Specifies the Content-Type HTTP header of error responses sent to theclient. The default value is
'text/html'.
- protocol_version¶
Specifies the HTTP version to which the server is conformant. It is sentin responses to let the client know the server’s communicationcapabilities for future requests. If set to
'HTTP/1.1', the server will permit HTTP persistent connections;however, your servermust then include an accurateContent-Lengthheader (usingsend_header()) in all of its responses to clients.For backwards compatibility, the setting defaults to'HTTP/1.0'.
- MessageClass¶
Specifies an
email.message.Message-like class to parse HTTPheaders. Typically, this is not overridden, and it defaults tohttp.client.HTTPMessage.
- responses¶
This attribute contains a mapping of error code integers to two-element tuplescontaining a short and long message. For example,
{code:(shortmessage,longmessage)}. Theshortmessage is usually used as themessage key in anerror response, andlongmessage as theexplain key. It is used bysend_response_only()andsend_error()methods.
A
BaseHTTPRequestHandlerinstance has the following methods:- handle()¶
Calls
handle_one_request()once (or, if persistent connections areenabled, multiple times) to handle incoming HTTP requests. You shouldnever need to override it; instead, implement appropriatedo_*()methods.
- handle_one_request()¶
This method will parse and dispatch the request to the appropriate
do_*()method. You should never need to override it.
- handle_expect_100()¶
When an HTTP/1.1 conformant server receives an
Expect:100-continuerequest header it responds back with a100Continuefollowed by200OKheaders.This method can be overridden to raise an error if the server does notwant the client to continue. For e.g. server can choose to send417ExpectationFailedas a response header andreturnFalse.Added in version 3.2.
- send_error(code,message=None,explain=None)¶
Sends and logs a complete error reply to the client. The numericcodespecifies the HTTP error code, withmessage as an optional, short, humanreadable description of the error. Theexplain argument can be used toprovide more detailed information about the error; it will be formattedusing the
error_message_formatattribute and emitted, aftera complete set of headers, as the response body. Theresponsesattribute holds the default values formessage andexplain thatwill be used if no value is provided; for unknown codes the default valuefor both is the string???. The body will be empty if the method isHEAD or the response code is one of the following:1xx,204NoContent,205ResetContent,304NotModified.Changed in version 3.4:The error response includes a Content-Length header.Added theexplain argument.
- send_response(code,message=None)¶
Adds a response header to the headers buffer and logs the acceptedrequest. The HTTP response line is written to the internal buffer,followed byServer andDate headers. The values for these two headersare picked up from the
version_string()anddate_time_string()methods, respectively. If the server does notintend to send any other headers using thesend_header()method,thensend_response()should be followed by anend_headers()call.Changed in version 3.3:Headers are stored to an internal buffer and
end_headers()needs to be called explicitly.
- send_header(keyword,value)¶
Adds the HTTP header to an internal buffer which will be written to theoutput stream when either
end_headers()orflush_headers()isinvoked.keyword should specify the header keyword, withvaluespecifying its value. Note that, after the send_header calls are done,end_headers()MUST BE called in order to complete the operation.Changed in version 3.2:Headers are stored in an internal buffer.
- send_response_only(code,message=None)¶
Sends the response header only, used for the purposes when
100Continueresponse is sent by the server to the client. The headers notbuffered and sent directly the output stream.If themessage is notspecified, the HTTP message corresponding the responsecode is sent.Added in version 3.2.
- end_headers()¶
Adds a blank line(indicating the end of the HTTP headers in the response)to the headers buffer and calls
flush_headers().Changed in version 3.2:The buffered headers are written to the output stream.
- flush_headers()¶
Finally send the headers to the output stream and flush the internalheaders buffer.
Added in version 3.3.
- log_request(code='-',size='-')¶
Logs an accepted (successful) request.code should specify the numericHTTP code associated with the response. If a size of the response isavailable, then it should be passed as thesize parameter.
- log_error(...)¶
Logs an error when a request cannot be fulfilled. By default, it passesthe message to
log_message(), so it takes the same arguments(format and additional values).
- log_message(format,...)¶
Logs an arbitrary message to
sys.stderr. This is typically overriddento create custom error logging mechanisms. Theformat argument is astandard printf-style format string, where the additional arguments tolog_message()are applied as inputs to the formatting. The clientip address and current date and time are prefixed to every message logged.
- version_string()¶
Returns the server software’s version string. This is a combination of the
server_versionandsys_versionattributes.
- date_time_string(timestamp=None)¶
Returns the date and time given bytimestamp (which must be
Noneor inthe format returned bytime.time()), formatted for a messageheader. Iftimestamp is omitted, it uses the current date and time.The result looks like
'Sun,06Nov199408:49:37GMT'.
- log_date_time_string()¶
Returns the current date and time, formatted for logging.
- address_string()¶
Returns the client address.
Changed in version 3.3:Previously, a name lookup was performed. To avoid name resolutiondelays, it now always returns the IP address.
- classhttp.server.SimpleHTTPRequestHandler(request,client_address,server,directory=None)¶
This class serves files from the directorydirectory and below,or the current directory ifdirectory is not provided, directlymapping the directory structure to HTTP requests.
Changed in version 3.7:Added thedirectory parameter.
Changed in version 3.9:Thedirectory parameter accepts apath-like object.
A lot of the work, such as parsing the request, is done by the base class
BaseHTTPRequestHandler. This class implements thedo_GET()anddo_HEAD()functions.The following are defined as class-level attributes of
SimpleHTTPRequestHandler:- server_version¶
This will be
"SimpleHTTP/"+__version__, where__version__isdefined at the module level.
- extensions_map¶
A dictionary mapping suffixes into MIME types, contains custom overridesfor the default system mappings. The mapping is used case-insensitively,and so should contain only lower-cased keys.
Changed in version 3.9:This dictionary is no longer filled with the default system mappings,but only contains overrides.
The
SimpleHTTPRequestHandlerclass defines the following methods:- do_HEAD()¶
This method serves the
'HEAD'request type: it sends the headers itwould send for the equivalentGETrequest. See thedo_GET()method for a more complete explanation of the possible headers.
- do_GET()¶
The request is mapped to a local file by interpreting the request as apath relative to the current working directory.
If the request was mapped to a directory, the directory is checked for afile named
index.htmlorindex.htm(in that order). If found, thefile’s contents are returned; otherwise a directory listing is generatedby calling thelist_directory()method. This method usesos.listdir()to scan the directory, and returns a404errorresponse if thelistdir()fails.If the request was mapped to a file, it is opened. Any
OSErrorexception in opening the requested file is mapped to a404,'Filenotfound'error. If there was an'If-Modified-Since'header in the request, and the file was not modified after this time,a304,'NotModified'response is sent. Otherwise, the contenttype is guessed by calling theguess_type()method, which in turnuses theextensions_map variable, and the file contents are returned.A
'Content-type:'header with the guessed content type is output,followed by a'Content-Length:'header with the file’s size and a'Last-Modified:'header with the file’s modification time.Then follows a blank line signifying the end of the headers, and then thecontents of the file are output.
For example usage, see the implementation of the
testfunctioninLib/http/server.py.Changed in version 3.7:Support of the
'If-Modified-Since'header.
TheSimpleHTTPRequestHandler class can be used in the followingmanner in order to create a very basic webserver serving files relative tothe current directory:
importhttp.serverimportsocketserverPORT=8000Handler=http.server.SimpleHTTPRequestHandlerwithsocketserver.TCPServer(("",PORT),Handler)ashttpd:print("serving at port",PORT)httpd.serve_forever()
SimpleHTTPRequestHandler can also be subclassed to enhance behavior,such as using different index file names by overriding the class attributeindex_pages.
- classhttp.server.CGIHTTPRequestHandler(request,client_address,server)¶
This class is used to serve either files or output of CGI scripts from thecurrent directory and below. Note that mapping HTTP hierarchic structure tolocal directory structure is exactly as in
SimpleHTTPRequestHandler.Note
CGI scripts run by the
CGIHTTPRequestHandlerclass cannot executeredirects (HTTP code 302), because code 200 (script output follows) issent prior to execution of the CGI script. This pre-empts the statuscode.The class will however, run the CGI script, instead of serving it as a file,if it guesses it to be a CGI script. Only directory-based CGI are used —the other common server configuration is to treat special extensions asdenoting CGI scripts.
The
do_GET()anddo_HEAD()functions are modified to run CGI scriptsand serve the output, instead of serving files, if the request leads tosomewhere below thecgi_directoriespath.The
CGIHTTPRequestHandlerdefines the following data member:- cgi_directories¶
This defaults to
['/cgi-bin','/htbin']and describes directories totreat as containing CGI scripts.
The
CGIHTTPRequestHandlerdefines the following method:- do_POST()¶
This method serves the
'POST'request type, only allowed for CGIscripts. Error 501, “Can only POST to CGI scripts”, is output when tryingto POST to a non-CGI url.
Note that CGI scripts will be run with UID of user nobody, for securityreasons. Problems with the CGI script will be translated to error 403.
Deprecated since version 3.13, will be removed in version 3.15:
CGIHTTPRequestHandleris being removed in 3.15. CGI has notbeen considered a good way to do things for well over a decade. This codehas been unmaintained for a while now and sees very little practical use.Retaining it could lead to furthersecurity considerations.
Command-line interface¶
http.server can also be invoked directly using the-mswitch of the interpreter. The following example illustrates how to servefiles relative to the current directory:
python-mhttp.server[OPTIONS][port]
The following options are accepted:
- port¶
The server listens to port 8000 by default. The default can be overriddenby passing the desired port number as an argument:
python-mhttp.server9000
- -b,--bind<address>¶
Specifies a specific address to which it should bind. Both IPv4 and IPv6addresses are supported. By default, the server binds itself to allinterfaces. For example, the following command causes the server to bindto localhost only:
python-mhttp.server--bind127.0.0.1
Added in version 3.4.
Changed in version 3.8:Support IPv6 in the
--bindoption.
- -d,--directory<dir>¶
Specifies a directory to which it should serve the files. By default,the server uses the current directory. For example, the following commanduses a specific directory:
python-mhttp.server--directory/tmp/
Added in version 3.7.
- -p,--protocol<version>¶
Specifies the HTTP version to which the server is conformant. By default,the server is conformant to HTTP/1.0. For example, the following commandruns an HTTP/1.1 conformant server:
python-mhttp.server--protocolHTTP/1.1
Added in version 3.11.
- --cgi¶
CGIHTTPRequestHandlercan be enabled in the command line by passingthe--cgioption:python-mhttp.server--cgi
Deprecated since version 3.13, will be removed in version 3.15:
http.servercommand line--cgisupport is being removedbecauseCGIHTTPRequestHandleris being removed.
Warning
CGIHTTPRequestHandler and the--cgi command-line optionare not intended for use by untrusted clients and may be vulnerableto exploitation. Always use within a secure environment.
- --tls-cert¶
Specifies a TLS certificate chain for HTTPS connections:
python-mhttp.server--tls-certfullchain.pem
Added in version 3.14.
- --tls-key¶
Specifies a private key file for HTTPS connections.
This option requires
--tls-certto be specified.Added in version 3.14.
- --tls-password-file¶
Specifies the password file for password-protected private keys:
python-mhttp.server \--tls-certcert.pem \--tls-keykey.pem \--tls-password-filepassword.txt
This option requires–tls-cert` to be specified.
Added in version 3.14.
Security considerations¶
SimpleHTTPRequestHandler will follow symbolic links when handlingrequests, this makes it possible for files outside of the specified directoryto be served.
Earlier versions of Python did not scrub control characters from thelog messages emitted to stderr frompython-mhttp.server or thedefaultBaseHTTPRequestHandler.log_messageimplementation. This could allow remote clients connecting to yourserver to send nefarious control codes to your terminal.
Changed in version 3.12:Control characters are scrubbed in stderr logs.