http.client
--- HTTP 協定用戶端¶
This module defines classes that implement the client side of the HTTP andHTTPS protocols. It is normally not used directly --- the moduleurllib.request
uses it to handle URLs that use HTTP and HTTPS.
也參考
TheRequests packageis recommended for a higher-level HTTP client interface.
備註
HTTPS support is only available if Python was compiled with SSL support(through thessl
module).
適用: not WASI.
此模組在 WebAssembly 平台上不起作用或無法使用。更多資訊請參閱WebAssembly 平台。
The module provides the following classes:
- classhttp.client.HTTPConnection(host,port=None,[timeout,]source_address=None,blocksize=8192)¶
An
HTTPConnection
instance represents one transaction with an HTTPserver. It should be instantiated by passing it a host and optional portnumber. If no port number is passed, the port is extracted from the hoststring if it has the formhost:port
, else the default HTTP port (80) isused. If the optionaltimeout parameter is given, blockingoperations (like connection attempts) will timeout after that many seconds(if it is not given, the global default timeout setting is used).The optionalsource_address parameter may be a tuple of a (host, port)to use as the source address the HTTP connection is made from.The optionalblocksize parameter sets the buffer size in bytes forsending a file-like message body.For example, the following calls all create instances that connect to the serverat the same host and port:
>>>h1=http.client.HTTPConnection('www.python.org')>>>h2=http.client.HTTPConnection('www.python.org:80')>>>h3=http.client.HTTPConnection('www.python.org',80)>>>h4=http.client.HTTPConnection('www.python.org',80,timeout=10)
在 3.2 版的變更:新增source_address。
在 3.4 版的變更:Thestrict parameter was removed. HTTP 0.9-style "Simple Responses" areno longer supported.
在 3.7 版的變更:新增blocksize 參數。
- classhttp.client.HTTPSConnection(host,port=None,*,[timeout,]source_address=None,context=None,blocksize=8192)¶
A subclass of
HTTPConnection
that uses SSL for communication withsecure servers. Default port is443
. Ifcontext is specified, itmust be assl.SSLContext
instance describing the various SSLoptions.Please readSecurity considerations for more information on best practices.
在 3.2 版的變更:新增source_address、context 與check_hostname。
在 3.2 版的變更:This class now supports HTTPS virtual hosts if possible (that is,if
ssl.HAS_SNI
is true).在 3.4 版的變更:Thestrict parameter was removed. HTTP 0.9-style "Simple Responses" areno longer supported.
在 3.4.3 版的變更:This class now performs all the necessary certificate and hostname checksby default. To revert to the previous, unverified, behavior
ssl._create_unverified_context()
can be passed to thecontextparameter.在 3.8 版的變更:This class now enables TLS 1.3
ssl.SSLContext.post_handshake_auth
for the defaultcontext orwhencert_file is passed with a customcontext.在 3.10 版的變更:This class now sends an ALPN extension with protocol indicator
http/1.1
when nocontext is given. Customcontext should setALPN protocols withset_alpn_protocols()
.在 3.12 版的變更:The deprecatedkey_file,cert_file andcheck_hostname parametershave been removed.
- classhttp.client.HTTPResponse(sock,debuglevel=0,method=None,url=None)¶
Class whose instances are returned upon successful connection. Notinstantiated directly by user.
在 3.4 版的變更:Thestrict parameter was removed. HTTP 0.9 style "Simple Responses" areno longer supported.
This module provides the following function:
- http.client.parse_headers(fp)¶
Parse the headers from a file pointerfp representing a HTTPrequest/response. The file has to be a
BufferedIOBase
reader(i.e. not text) and must provide a validRFC 2822 style header.This function returns an instance of
http.client.HTTPMessage
that holds the header fields, but no payload(the same asHTTPResponse.msg
andhttp.server.BaseHTTPRequestHandler.headers
).After returning, the file pointerfp is ready to read the HTTP body.備註
parse_headers()
does not parse the start-line of a HTTP message;it only parses theName:value
lines. The file has to be ready toread these field lines, so the first line should already be consumedbefore calling the function.
The following exceptions are raised as appropriate:
- exceptionhttp.client.HTTPException¶
The base class of the other exceptions in this module. It is a subclass of
Exception
.
- exceptionhttp.client.NotConnected¶
A subclass of
HTTPException
.
- exceptionhttp.client.InvalidURL¶
A subclass of
HTTPException
, raised if a port is given and is eithernon-numeric or empty.
- exceptionhttp.client.UnknownProtocol¶
A subclass of
HTTPException
.
- exceptionhttp.client.UnknownTransferEncoding¶
A subclass of
HTTPException
.
- exceptionhttp.client.UnimplementedFileMode¶
A subclass of
HTTPException
.
- exceptionhttp.client.IncompleteRead¶
A subclass of
HTTPException
.
- exceptionhttp.client.ImproperConnectionState¶
A subclass of
HTTPException
.
- exceptionhttp.client.CannotSendRequest¶
A subclass of
ImproperConnectionState
.
- exceptionhttp.client.CannotSendHeader¶
A subclass of
ImproperConnectionState
.
- exceptionhttp.client.ResponseNotReady¶
A subclass of
ImproperConnectionState
.
- exceptionhttp.client.BadStatusLine¶
A subclass of
HTTPException
. Raised if a server responds with a HTTPstatus code that we don't understand.
- exceptionhttp.client.LineTooLong¶
A subclass of
HTTPException
. Raised if an excessively long lineis received in the HTTP protocol from the server.
- exceptionhttp.client.RemoteDisconnected¶
A subclass of
ConnectionResetError
andBadStatusLine
. RaisedbyHTTPConnection.getresponse()
when the attempt to read the responseresults in no data read from the connection, indicating that the remote endhas closed the connection.在 3.5 版被加入:Previously,
BadStatusLine
('')
was raised.
The constants defined in this module are:
- http.client.HTTP_PORT¶
The default port for the HTTP protocol (always
80
).
- http.client.HTTPS_PORT¶
The default port for the HTTPS protocol (always
443
).
- http.client.responses¶
This dictionary maps the HTTP 1.1 status codes to the W3C names.
Example:
http.client.responses[http.client.NOT_FOUND]
is'NotFound'
.
SeeHTTP 狀態碼 for a list of HTTP status codes that areavailable in this module as constants.
HTTPConnection 物件¶
HTTPConnection
instances have the following methods:
- HTTPConnection.request(method,url,body=None,headers={},*,encode_chunked=False)¶
This will send a request to the server using the HTTP requestmethodmethod and the request URIurl. The providedurl must bean absolute path to conform withRFC 2616 §5.1.2(unless connecting to an HTTP proxy server or using the
OPTIONS
orCONNECT
methods).Ifbody is specified, the specified data is sent after the headers arefinished. It may be a
str
, abytes-like object, anopenfile object, or an iterable ofbytes
. Ifbodyis a string, it is encoded as ISO-8859-1, the default for HTTP. If itis a bytes-like object, the bytes are sent as is. If it is afileobject, the contents of the file is sent; this file object shouldsupport at least theread()
method. If the file object is aninstance ofio.TextIOBase
, the data returned by theread()
method will be encoded as ISO-8859-1, otherwise the data returned byread()
is sent as is. Ifbody is an iterable, the elements of theiterable are sent as is until the iterable is exhausted.Theheaders argument should be a mapping of extra HTTP headers to sendwith the request. AHost headermust be provided to conform withRFC 2616 §5.1.2(unless connecting to an HTTP proxy server or using the
OPTIONS
orCONNECT
methods).Ifheaders contains neither Content-Length nor Transfer-Encoding,but there is a request body, one of thoseheader fields will be added automatically. Ifbody is
None
, the Content-Length header is set to0
formethods that expect a body (PUT
,POST
, andPATCH
). Ifbody is a string or a bytes-like object that is not also afile, the Content-Length header isset to its length. Any other type ofbody (filesand iterables in general) will be chunk-encoded, and theTransfer-Encoding header will automatically be set instead ofContent-Length.Theencode_chunked argument is only relevant if Transfer-Encoding isspecified inheaders. Ifencode_chunked is
False
, theHTTPConnection object assumes that all encoding is handled by thecalling code. If it isTrue
, the body will be chunk-encoded.For example, to perform a
GET
request tohttps://docs.python.org/3/
:>>>importhttp.client>>>host="docs.python.org">>>conn=http.client.HTTPSConnection(host)>>>conn.request("GET","/3/",headers={"Host":host})>>>response=conn.getresponse()>>>print(response.status,response.reason)200 OK
備註
Chunked transfer encoding has been added to the HTTP protocolversion 1.1. Unless the HTTP server is known to handle HTTP 1.1,the caller must either specify the Content-Length, or must pass a
str
or bytes-like object that is not also a file as thebody representation.在 3.2 版的變更:body can now be an iterable.
在 3.6 版的變更:If neither Content-Length nor Transfer-Encoding are set inheaders, file and iterablebody objects are now chunk-encoded.Theencode_chunked argument was added.No attempt is made to determine the Content-Length for fileobjects.
- HTTPConnection.getresponse()¶
Should be called after a request is sent to get the response from the server.Returns an
HTTPResponse
instance.備註
Note that you must have read the whole response before you can send a newrequest to the server.
在 3.5 版的變更:If a
ConnectionError
or subclass is raised, theHTTPConnection
object will be ready to reconnect whena new request is sent.
- HTTPConnection.set_debuglevel(level)¶
Set the debugging level. The default debug level is
0
, meaning nodebugging output is printed. Any value greater than0
will cause allcurrently defined debug output to be printed to stdout. Thedebuglevel
is passed to any newHTTPResponse
objects that are created.在 3.1 版被加入.
- HTTPConnection.set_tunnel(host,port=None,headers=None)¶
Set the host and the port for HTTP Connect Tunnelling. This allows runningthe connection through a proxy server.
Thehost andport arguments specify the endpoint of the tunneled connection(i.e. the address included in the CONNECT request,not the address of theproxy server).
Theheaders argument should be a mapping of extra HTTP headers to send withthe CONNECT request.
As HTTP/1.1 is used for HTTP CONNECT tunnelling request,as per the RFC, a HTTP
Host:
header must be provided, matching the authority-form of the request targetprovided as the destination for the CONNECT request. If a HTTPHost:
header is not provided via the headers argument, one is generated andtransmitted automatically.For example, to tunnel through a HTTPS proxy server running locally on port8080, we would pass the address of the proxy to the
HTTPSConnection
constructor, and the address of the host that we eventually want to reach totheset_tunnel()
method:>>>importhttp.client>>>conn=http.client.HTTPSConnection("localhost",8080)>>>conn.set_tunnel("www.python.org")>>>conn.request("HEAD","/index.html")
在 3.2 版被加入.
在 3.12 版的變更:HTTP CONNECT tunnelling requests use protocol HTTP/1.1, upgraded fromprotocol HTTP/1.0.
Host:
HTTP headers are mandatory for HTTP/1.1, soone will be automatically generated and transmitted if not provided inthe headers argument.
- HTTPConnection.get_proxy_response_headers()¶
Returns a dictionary with the headers of the response received fromthe proxy server to the CONNECT request.
If the CONNECT request was not sent, the method returns
None
.在 3.12 版被加入.
- HTTPConnection.connect()¶
Connect to the server specified when the object was created. By default,this is called automatically when making a request if the client does notalready have a connection.
引發一個附帶引數
self
、host
、port
的稽核事件http.client.connect
。
- HTTPConnection.close()¶
Close the connection to the server.
- HTTPConnection.blocksize¶
Buffer size in bytes for sending a file-like message body.
在 3.7 版被加入.
As an alternative to using therequest()
method described above, you canalso send your request step by step, by using the four functions below.
- HTTPConnection.putrequest(method,url,skip_host=False,skip_accept_encoding=False)¶
This should be the first call after the connection to the server has beenmade. It sends a line to the server consisting of themethod string,theurl string, and the HTTP version (
HTTP/1.1
). To disable automaticsending ofHost:
orAccept-Encoding:
headers (for example to acceptadditional content encodings), specifyskip_host orskip_accept_encodingwith non-False values.
- HTTPConnection.putheader(header,argument[,...])¶
Send anRFC 822-style header to the server. It sends a line to the serverconsisting of the header, a colon and a space, and the first argument. If morearguments are given, continuation lines are sent, each consisting of a tab andan argument.
- HTTPConnection.endheaders(message_body=None,*,encode_chunked=False)¶
Send a blank line to the server, signalling the end of the headers. Theoptionalmessage_body argument can be used to pass a message bodyassociated with the request.
Ifencode_chunked is
True
, the result of each iteration ofmessage_body will be chunk-encoded as specified inRFC 7230,Section 3.3.1. How the data is encoded is dependent on the type ofmessage_body. Ifmessage_body implements thebuffer interface the encoding will result in a single chunk.Ifmessage_body is acollections.abc.Iterable
, each iterationofmessage_body will result in a chunk. Ifmessage_body is afile object, each call to.read()
will result in a chunk.The method automatically signals the end of the chunk-encoded dataimmediately aftermessage_body.備註
Due to the chunked encoding specification, empty chunksyielded by an iterator body will be ignored by the chunk-encoder.This is to avoid premature termination of the read of the request bythe target server due to malformed encoding.
在 3.6 版的變更:Added chunked encoding support and theencode_chunked parameter.
- HTTPConnection.send(data)¶
Send data to the server. This should be used directly only after the
endheaders()
method has been called and beforegetresponse()
iscalled.引發一個附帶引數
self
、data
的稽核事件http.client.send
。
HTTPResponse 物件¶
AnHTTPResponse
instance wraps the HTTP response from theserver. It provides access to the request headers and the entitybody. The response is an iterable object and can be used in a withstatement.
在 3.5 版的變更:Theio.BufferedIOBase
interface is now implemented andall of its reader operations are supported.
- HTTPResponse.read([amt])¶
Reads and returns the response body, or up to the nextamt bytes.
- HTTPResponse.readinto(b)¶
Reads up to the next len(b) bytes of the response body into the bufferb.Returns the number of bytes read.
在 3.3 版被加入.
- HTTPResponse.getheader(name,default=None)¶
Return the value of the headername, ordefault if there is no headermatchingname. If there is more than one header with the namename,return all of the values joined by ', '. Ifdefault is any iterable otherthan a single string, its elements are similarly returned joined by commas.
- HTTPResponse.getheaders()¶
Return a list of (header, value) tuples.
- HTTPResponse.fileno()¶
Return the
fileno
of the underlying socket.
- HTTPResponse.msg¶
A
http.client.HTTPMessage
instance containing the responseheaders.http.client.HTTPMessage
is a subclass ofemail.message.Message
.
- HTTPResponse.version¶
HTTP protocol version used by server. 10 for HTTP/1.0, 11 for HTTP/1.1.
- HTTPResponse.url¶
URL of the resource retrieved, commonly used to determine if a redirect was followed.
- HTTPResponse.headers¶
Headers of the response in the form of an
email.message.EmailMessage
instance.
- HTTPResponse.status¶
Status code returned by server.
- HTTPResponse.reason¶
Reason phrase returned by server.
- HTTPResponse.debuglevel¶
A debugging hook. If
debuglevel
is greater than zero, messageswill be printed to stdout as the response is read and parsed.
- HTTPResponse.closed¶
Is
True
if the stream is closed.
範例¶
Here is an example session that uses theGET
method:
>>>importhttp.client>>>conn=http.client.HTTPSConnection("www.python.org")>>>conn.request("GET","/")>>>r1=conn.getresponse()>>>print(r1.status,r1.reason)200 OK>>>data1=r1.read()# This will return entire content.>>># The following example demonstrates reading data in chunks.>>>conn.request("GET","/")>>>r1=conn.getresponse()>>>whilechunk:=r1.read(200):...print(repr(chunk))b'<!doctype html>\n<!--[if"......>>># Example of an invalid request>>>conn=http.client.HTTPSConnection("docs.python.org")>>>conn.request("GET","/parrot.spam")>>>r2=conn.getresponse()>>>print(r2.status,r2.reason)404 Not Found>>>data2=r2.read()>>>conn.close()
Here is an example session that uses theHEAD
method. Note that theHEAD
method never returns any data.
>>>importhttp.client>>>conn=http.client.HTTPSConnection("www.python.org")>>>conn.request("HEAD","/")>>>res=conn.getresponse()>>>print(res.status,res.reason)200 OK>>>data=res.read()>>>print(len(data))0>>>data==b''True
Here is an example session that uses thePOST
method:
>>>importhttp.client,urllib.parse>>>params=urllib.parse.urlencode({'@number':12524,'@type':'issue','@action':'show'})>>>headers={"Content-type":"application/x-www-form-urlencoded",..."Accept":"text/plain"}>>>conn=http.client.HTTPConnection("bugs.python.org")>>>conn.request("POST","",params,headers)>>>response=conn.getresponse()>>>print(response.status,response.reason)302 Found>>>data=response.read()>>>datab'Redirecting to <a href="https://bugs.python.org/issue12524">https://bugs.python.org/issue12524</a>'>>>conn.close()
Client side HTTPPUT
requests are very similar toPOST
requests. Thedifference lies only on the server side where HTTP servers will allow resources tobe created viaPUT
requests. It should be noted that custom HTTP methodsare also handled inurllib.request.Request
by setting the appropriatemethod attribute. Here is an example session that uses thePUT
method:
>>># This creates an HTTP request>>># with the content of BODY as the enclosed representation>>># for the resource http://localhost:8080/file...>>>importhttp.client>>>BODY="***filecontents***">>>conn=http.client.HTTPConnection("localhost",8080)>>>conn.request("PUT","/file",BODY)>>>response=conn.getresponse()>>>print(response.status,response.reason)200, OK
HTTPMessage 物件¶
- classhttp.client.HTTPMessage(email.message.Message)¶
Anhttp.client.HTTPMessage
instance holds the headers from an HTTPresponse. It is implemented using theemail.message.Message
class.