+ hhcsJ^RIHtHtHtHtHtHtHtHtH t H t ^RI H t H t HtHtHtHtHt^RIHtHtHt^RIHtHt^RIHt^RIHtHtHtH t H!t!H"t"H#t#H$t$H%t%H&t&^RI'H(t(H)t)H*t*^RI+H,t,H-t-.ROt.!R R ]*]*R 7t/!RR ]*]*R 7t0Rt1RRlt2RRlt3!RR 4t4R#)) AnyCallablecastDictListOptionaloverloadTupleTypeUnion)ConnectionClosedData EndOfMessageEventInformationalResponseRequestResponse)get_comma_headerhas_expect_100_continueset_comma_header)READERS ReadersType) ReceiveBuffer) _SWITCH_CONNECT_SWITCH_UPGRADECLIENTConnectionStateDONEERRORMIGHT_SWITCH_PROTOCOL SEND_BODYSERVERSWITCHED_PROTOCOL)LocalProtocolErrorRemoteProtocolErrorSentinel)WRITERS WritersType Connection NEED_DATAPAUSEDcs]tRt^3tRtR#)r(N__name__ __module__ __qualname____firstlineno____static_attributes__r*4/usr/lib/python3.14/site-packages/h11/_connection.pyr(r(3r1)Z metaclasscs]tRt^7tRtR#)r)r*Nr+r*r1r2r)r)7r3r1csRV^8dQhR\\\3,R\/#eventreturn)r rrboolformat"r2 __annotate__r<Ts$uWh./Dr1csl\VPR4pRV9dR#\VRR4R8dR#R#) connectioncloseF http_version1.1T)rheadersZgetattr)r6 connection& r2 _keep_aliverDTs4!%--?J:unf-6 r1c sV^8dQhR\R\\\3,R\\ \\R,\\ ,3,3,/#)r5request_methodr6r7r*)bytesr rrrZstrintr9r;r2r<r<]sJ0 0 0 "'(9":0  3eBis+, ,-0 r1csv\V4\Jd>VPR9g+VR8Xg$VR8Xd^VPu;8:dR8dMMR#\VPR4pV'dR #\VPR4pV'dR\ V^,433#\V4\ JdR#R #) HEADCONNECT,content-lengthtransfer-encodingcontent-length)rHi0)rL)r)chunkedr*)http/1.0r*)typer status_coderrArGr)rEr6Ztransfer_encodingsZcontent_lengths&& r2 _body_framingrT]s* E{h    +(*,8I8I1OC1O+ +*%--9MN'u}}6GHO 3q'9#:"<== E{g''r1cs a]tRt^toRt]3V3RlRllt]V3RlRl4t]V3RlRl4t ]V3RlR l4t ]V3R lR l4t V3R lR lt V3RlRlt V3RlRltV3RlRltV3RlRltR0V3RlRllt]V3RlRl4tV3RlRltV3RlRltV3RlR lt]V3R!lR"l4t]V3R#lR$l4t]V3R%lR&l4tV3R'lR(ltV3R)lR*ltV3R+lR,ltV3R-lR.ltR/tVtR#)1r'aAn object encapsulating the state of an HTTP connection. Args: our_role: If you're implementing a client, pass :data:`h11.CLIENT`. If you're implementing a server, pass :data:`h11.SERVER`. max_incomplete_event_size (int): The maximum number of bytes we're willing to buffer of an incomplete event. In practice this mostly sets a limit on the maximum size of the request/response line + headers. If this is exceeded, then :meth:`next_event` will raise :exc:`RemoteProtocolError`. c:<V^8dQhRS[S[,RS[RR/#)r5our_rolemax_incomplete_event_sizer7N)r r$rGr: __classdict__"r2r<Connection.__annotate__s-%8%8x.%8$'%8  %8r1csW nV\\39d\RV: 24hWnVV\Jd \VnM \Vn\ 4VnVPVPR\4Vn VPVP R\4Vn \4VnRVnRVnRVnRVnR#)zexpected CLIENT or SERVER, not NF)_max_incomplete_event_sizerr Z ValueErrorrV their_roler_cstate_get_io_objectr%_writerr_readerr_receive_buffer_receive_buffer_closedtheir_http_version_request_method"client_is_waiting_for_100_continue)selfrVrW&&&r2__init__ZConnection.__init__s +D' FF+ +>xlKL L  v $DO$DO&( **4==$H **4??D'J  -',#480438/r1csV<V^8dQhRS[S[S[,S[S[,3,/#r5r7)rr r$rXrZr2r<r[s&))T(^T(^;<)r1c s@\VPP4#)zqA dictionary like:: {CLIENT: , SERVER: } See :ref:`state-machine` for details. )dictr^statesrg&r2rlZConnection.statessDLL''((r1c0<V^8dQhRS[S[,/#rjr r$rXrZr2r<r[s224>2r1c PVPPVP,#)zZThe current state of whichever role we are playing. See :ref:`state-machine` for details. )r^rlrVrmrnr2 our_stateZConnection.our_states ||""4==11r1crorjrprXrZr2r<r[s44T(^4r1c rq)z^The current state of whichever role we are NOT playing. See :ref:`state-machine` for details. )r^rlr]rmrnr2 their_stateZConnection.their_states ||""4??33r1cs <V^8dQhRS[/#rj)r8rXrZr2r<r[sUU4Ur1csNVP\J;'d VP#N)r]rrfrmrnr2!they_are_waiting_for_100_continueZ,Connection.they_are_waiting_for_100_continues&(TTT-T-TTr1c<V^8dQhRR/#r5r7Nr*rXrZr2r<r[s33$3r1c s\VPP4pVPP4RVnVP V4R#)aIAttempt to reset our connection state for a new request/response cycle. If both client and server are in :data:`DONE` state, then resets them both to :data:`IDLE` state in preparation for a new request/response cycle on this same connection. Otherwise, raises a :exc:`LocalProtocolError`. See :ref:`keepalive-and-pipelining`. N)rkr^rlstart_next_cyclere_respond_to_state_changes)rg old_statesrCr2rxZConnection.start_next_cycles@$,,--.  %%'# &&z2r1cs4<V^8dQhRS[S[,RR/#)r5roler7NrprXrZr2r<r[s334>3d3r1cs\VPP4pVPPV4VP V4R#rt)rkr^rlZ process_errorry)rgr{rz&& r2_process_errorZConnection._process_errors6$,,--.  ""4( &&z2r1cF<V^8dQhRS[RS[S[S[,,/#r4)rrr r$rXrZr2r<r[s$  % HT(^4L r1cs\V4\JdVP^e8Xd\#\V4\JdC\ VP P9d$^VPu;8:dR8d \ #R#R#)ierKN)rQrrRrrrr^Zpending_switch_proposalsrgr6&&r2_server_switch_eventZConnection._server_switch_eventsc ;/ /E4E4E4L" " ;( "4<<#H#HH5,,2s2&&3r1crU)r5r{r6r7N)r r$rrXrZr2r<r[s&.:.:4>.:%.:D.:r1cs\VPP4pV\Jd\ V4\ JdlVP R8Xd VPP\4\VPR4'd VPP\4RpV\JdVPV4pVPPV\ V4V4\ V4\ JdVP VnWP JdW\ V4\ \"\$39d8\'\(\ \"\$3,V4pVP*Vn\ V4\ \"39dK\/\'\(\ \"3,V44'gVPP14\ V4\ Jd\3V4'dRVn\ V4\$\"39dRVnV\Jd"\ V4\6\839dRVnVP;W24R#)rJsupgradeNTF)rkr^rlrrQrZmethodZprocess_client_switch_proposalrrrArr rZ process_eventrer]rrrr r?rdrDZprocess_keep_alive_disabledrrfr r ry)rgr{r6rzZserver_switch_events&&& r2_process_eventZConnection._process_events$,,--. 6>d5kW4||z) ;;OL z:: ;;OL" 6>"&";";E"B  ""4e6IJ ;' !#(<d5kdL-AA6;D 3 &&z9r1c s<V^8dQhRS[S[,RS[S[,RS[S[S[3,RS[S[RS[3,,/#)r5r{r6io_dictr7.) r r$rrr rr&rrrXrZr2r<r[@sS..8n..{K/0 . (38$ % .r1cs.VPPV,pV\Jd^\\ \ VP 4\ \\\3,V44wrVV\,V,!V!#VPW34#rt) r^rlrrTrrFrer rrZget)rgr{r6rstate framing_typeZargss&&&& r2r_ZConnection._get_io_object@s} ##D) I "/UD0014gx>O8PRW3X" L9%l3T: :;;}- -r1Ncsp<V^8dQhRS[S[S[,S[S[,3,RS[S[,RR/#)r5rzr6r7N)rr r$rrrXrZr2r<r[VsD P Phh78 P P  Pr1cs&VPWP,8wd'VPVPV\4VnVP WP ,8wd)VPVP V\4VnR#R#rt) rrrVr_r%r`rsr]rra)rgrzr6rhr2ryZ$Connection._respond_to_state_changesVse >>Z 6 6..t}}eWMDL   z//: :..twODL ;r1cs6<V^8dQhRS[S[S[3,/#rj)rrFr8rXrZr2r<r[bs JJuUD[1Jr1c sD\VP4VP3#)a:Data that has been received, but not yet processed, represented as a tuple with two elements, where the first is a byte-string containing the unprocessed data itself, and the second is a bool that is True if the receive connection was closed. See :ref:`switching-protocols` for discussion of why you'd want this. )rFrbrcrmrnr2 trailing_dataZConnection.trailing_dataas d**+T-H-HIIr1c$<V^8dQhRS[RR/#)r5datar7N)rFrXrZr2r<r[ls,/,/,/4,/r1c sV'd9VP'd \R4hV;PV, unR#RVnR#)aAdd data to our internal receive buffer. This does not actually do any processing on the data, just stores it. To trigger processing, you have to call :meth:`next_event`. Args: data (:term:`bytes-like object`): The new data that was just received. Special case: If *data* is an empty byte-string like ``b""``, then this indicates that the remote side has closed the connection (end of file). Normally this is convenient, because standard Python APIs like :meth:`file.read` or :meth:`socket.recv` use ``b""`` to indicate end-of-file, while other failures to read are indicated using other mechanisms like raising :exc:`TimeoutError`. When using such an API you can just blindly pass through whatever you get from ``read`` to :meth:`receive_data`, and everything will work. But, if you have an API where reading an empty string is a valid non-EOF condition, then you need to be aware of this and make sure to check for such strings and avoid passing them to :meth:`receive_data`. Returns: Nothing, but after calling this you should call :meth:`next_event` to parse the newly received data. Raises: RuntimeError: Raised if you pass an empty *data*, indicating EOF, and then pass a non-empty *data*, indicating more data that somehow arrived after the EOF. (Calling ``receive_data(b"")`` multiple times is fine, and equivalent to calling it once.) z(received close, then received more data?TN)rcZ RuntimeErrorrb)rgrrr2 receive_dataZConnection.receive_datals9N ***"#MNN  D ( *.D 'r1cZ<V^8dQhRS[S[S[S[,S[S[,3,/#rjr rr r(r)rXrZr2r<r[s) ud9otF|3 4r1csVPpV\JdVP'd\#V\Jg V\ Jd\#VP VP4pVffVP'gTVP'dB\VP R4'dVP P4pM \4pVf\pV#)Nread_eof) rsrrbr)rr!rarcZhasattrrr r()rgrr6& r2_extract_next_receive_eventZ&Connection._extract_next_receive_events   D=T111M ) )U6G-GM T112 ='''D,G,G,G 4<<44 LL113E,.E =E r1crrjrrXrZr2r<r[s(??E%i$v,"FG?r1c sBVP\Jd \R4hVP4pV\\ 39d+VP VP\\V44V\JdO\VP4VP8d\RRR7hVP'd \R4hV# \dNpTPTP4\!T\"4'dTP%4Rp?R#hRp?ii;i)anParse the next event out of our receive buffer, update our internal state, and return it. This is a mutating operation -- think of it like calling :func:`next` on an iterator. Returns: : One of three things: 1) An event object -- see :ref:`events`. 2) The special constant :data:`NEED_DATA`, which indicates that you need to read more data from your socket and pass it to :meth:`receive_data` before this method will be able to return any more events. 3) The special constant :data:`PAUSED`, which indicates that we are not in a state where we can process incoming data (usually because the peer has finished their part of the current request/response cycle, and you have not yet called :meth:`start_next_cycle`). See :ref:`flow-control` for details. Raises: RemoteProtocolError: The peer has misbehaved. You should close the connection (possibly after sending some kind of 4xx response). Once this method returns :class:`ConnectionClosed` once, then all subsequent calls will also return :class:`ConnectionClosed`. If this method raises any exception besides :exc:`RemoteProtocolError` then that's a bug -- if it happens please file a bug report! If this method raises any exception then it also sets :attr:`Connection.their_state` to :data:`ERROR` -- see :ref:`error-handling` for discussion. z+Can't receive data when peer state is ERRORzReceive buffer too longi)Zerror_status_hintz#peer unexpectedly closed connectionN)rsrr#rr(r)rr]rrZlenrbr\rcZ BaseExceptionr}Z isinstancer"Z!_reraise_as_remote_protocol_error)rgr6Zexcrr2 next_eventZConnection.next_eventsP   u $%&ST T 446EY//##DOOT%5GH !t++,t/N/NN.1S.....STTL     0#1225577  s%BC9 C DADDDcr)r5r6r7N)r rXrZr2r<r[s  * t r1cR#rtr*rrr2sendConnection.send r1csH<V^8dQhRS[S[S[S[S[S[3,RS[/#r4)r rrrr r rFrXrZr2r<r[s.  7$98T<WX  r1crrtr*rrr2rrs r1c6<V^8dQhRS[RS[S[,/#r4rrrFrXrZr2r<r[s  % HUO r1crrtr*rrr2rrrr1crr4rrXrZr2r<r[s''%'HUO'r1c sRVPV4pVfR#RPV4#)aCConvert a high-level event into bytes that can be sent to the peer, while updating our internal state machine. Args: event: The :ref:`event ` to send. Returns: If ``type(event) is ConnectionClosed``, then returns ``None``. Otherwise, returns a :term:`bytes-like object`. Raises: LocalProtocolError: Sending this event at this time would violate our understanding of the HTTP/1.1 protocol. If this method raises any exception then it also sets :attr:`Connection.our_state` to :data:`ERROR` -- see :ref:`error-handling` for discussion. Nr1)send_with_data_passthroughZjoin)rgr6 data_listr|r2rrs,*33E:  88I& &r1cr~r4)rrrrFrXrZr2r<r[ s$(4;:Or1c srVP\Jd \R4h\V4\JdVP V4pVP pVPVPV4\V4\JdR#.pV!WP4V# TPTP4h;i)a@Identical to :meth:`send`, except that in situations where :meth:`send` returns a single :term:`bytes-like object`, this instead returns a list of them -- and when sending a :class:`Data` event, this list is guaranteed to contain the exact object you passed in as :attr:`Data.data`. See :ref:`sendfile` for discussion. z'Can't send data when our state is ERRORN) rrrr"rQr&_clean_up_response_headers_for_sendingr`rrVr Zappendr})rgr6ZwriterrrSr2rZ%Connection.send_with_data_passthrough s >>U "$%NO O E{h&CCEJ \\F    u 5E{.. *, u../       . sABBB6crvrwr*rXrZr2r<r[As++T+r1c s<VPVP4R#)zNotify the state machine that we failed to send the data it gave us. This causes :attr:`Connection.our_state` to immediately become :data:`ERROR` -- see :ref:`error-handling` for discussion. N)r}rVrmrnr2 send_failedZConnection.send_failedAs DMM*r1cs&<V^8dQhRS[RS[/#)r5responser7)rrXrZr2r<r[Zs9 9 x9 H9 r1cs~VPpRp\\VP4pVR8XdRp\ WA4wrVVR 9d\\ VR.4pVP eVP R8d"\ VR.4pVPR8wdRpM\ VRR.4pVPP'd V'dN\\VR44pVPR 4VPR 4\ VR\V44p\VVPVP VP"R 7#) FrIsGETrNr@rMTschunkedr=s keep-aliver>)rArRr?reason)rOrP)rArrFrerTrrdr^Z keep_aliveZsetrZdiscardZaddZsortedrrRr?r)rgrrAZ need_closeZmethod_for_choosing_headersrZ_rBs&& r2rZ1Connection._clean_up_response_headers_for_sendingZs)"" '+5$2F2F&G# &' 1*0 ''(CN 2 2'w0A2FG&&.$2I2IF2R +74H"M ''72!%J*74H:,W||&&&*-g}EFJ   } - NN8 $&w vj?QRG ,,!..??   r1) r^r\rarbrcrer`rfrVrdr]rt)r,r-r.r/Z__doc__!DEFAULT_MAX_INCOMPLETE_EVENT_SIZEriZpropertyrlrrrsrurxr}rrr_ryrrrrrrrrrr0Z__classdictcell__)rYs@r2r'r'sG $*K%8%8N))22 44 UU33(33  .:.:`.., P PJJ,/,/\8??B      ''6B++29 9 r1N)r'r(r)i@)5Ztypingrrrrrrrrr r Z_eventsr r r rrrrZ_headersrrrZ_readersrrZ_receivebufferrZ_staterrrrrrrrr r!Z_utilr"r#r$Z_writersr%r&Z__all__r(r)rrDrTr'r*r1r2rs   RQ*)    + 0 H  X %.!0 t| | r1