| Server IP : 121.121.20.254 / Your IP : 216.73.217.141 Web Server : Microsoft-IIS/10.0 System : Windows NT WEB-SERVER 10.0 build 20348 (Windows Server 2022) AMD64 User : IUSR ( 0) PHP Version : 8.3.28 Disable Function : NONE MySQL : ON | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : C:/Python315/Lib/http/__pycache__/ |
Upload File : |
R
>lqj�� c � � Q s ] PHs] PHs] PHs] PHs] PHs] PHs] PH s] PH$s ] PH(s] QH0G
s
, Q8Ns]PsQsQsQsQsQs\ 2 O- \O. O0 2 \O. O0 O3 2 T t- tF D p U O4 aJ to sQs]ds]dsQ9s\O@ Q2 OB s"\O@ Q2 OF s$\O@ Q2 s%\O@ Q2 s&. Q:ls'Q;Q ks(Q Q ks) Q Q \OT OV 2 s,Q! s-\,1Q" ks.\,1Q#P-Q$ kks/ Q% Q\O` 2 s1Q& s2 Q' Q2 s3 ] PH�s4 Q( Q)\32 s5\Om Q)2 Q* Q\82 s9 Q+ Q\92 s: Q, Q
\92 s; Q- Q\92 s< Q. Q\92 s= Q/ Q\92 s> Q0 Q \92 s? Q1 Q\92 s@ Q2 Q\@2 sA Q3 Q
\@2 sB Q4 Q\@2 sC Q5 Q\92 sD Q6 Q\92 sE Q7 Q\F\D2 sG\9sHP! t to h \7 c K�h 9 h)<a�
HTTP/1.1 client library
<intro stuff goes here>
<other stuff, too>
HTTPConnection goes through a number of "states", which define when a client
may legally make another request or fetch the response for a particular
request. This diagram details these state transitions:
(null)
|
| HTTPConnection()
v
Idle
|
| putrequest()
v
Request-started
|
| ( putheader() )* endheaders()
v
Request-sent
|\_____________________________
| | getresponse() raises
| response = getresponse() | ConnectionError
v v
Unread-response Idle
[Response-headers-read]
|\____________________
| |
| response.read() | putrequest()
v v
Idle Req-started-unread-response
______/|
/ |
response.read() | | ( putheader() )* endheaders()
v v
Request-started Req-sent-unread-response
|
| response.read()
v
Request-sent
This diagram presents the following rules:
-- a second request may not be started until {response-headers-read}
-- a response [object] cannot be retrieved until {request-sent}
-- there is no differentiation between an unread response body and a
partially read response body
Note: this enforcement is applied by the HTTPConnection class. The
HTTPResponse class does not enforce this state machine, which
implies sophisticated clients may accelerate the request/response
pipeline. Caution should be taken, though: accelerating the states
beyond the above pattern may imply knowledge of the server's
connection-close behavior for certain requests. For example, it
is impossible to tell whether the server will close the connection
UNTIL the response headers have been read; this means that further
requests cannot be placed into the pipeline until it is known that
the server will NOT be closing the connection.
Logical State __state __response
------------- ------- ----------
Idle _CS_IDLE None
Request-started _CS_REQ_STARTED None
Request-sent _CS_REQ_SENT None
Unread-response _CS_IDLE <response_class>
Req-started-unread-response _CS_REQ_STARTED <response_class>
Req-sent-unread-response _CS_REQ_SENT <response_class>
)�urlsplit�HTTPResponse�HTTPConnection�
HTTPException�NotConnected�UnknownProtocol�UnknownTransferEncoding�UnimplementedFileMode�IncompleteRead�
InvalidURL�ImproperConnectionState�CannotSendRequest�CannotSendHeader�ResponseNotReady�
BadStatusLine�LineTooLong�RemoteDisconnected� �UNKNOWN�IdlezRequest-startedzRequest-senti s [^:\s][^:\r\n]*s \n(?![ \t])|\r(?![ \t\n])z[ - ]z[ -]c
� � U O Q2 ! [ co o[ SO SO SO SO
SO
2 8 QXO SO
8Q
QS8 Q02 PgPo=hh 9 h)z<Call data.encode("latin-1") but show a better error message.�latin-1z (z.20z) is not valid Latin-1. Use z9.encode('utf-8') if you want to send it encoded in UTF-8.)�encode�UnicodeEncodeError�encoding�object�start�end�title)�data�name�errs && � C:\Python315\\Lib\http\client.py�_encoder"