B Ceg@sfddlmZmZmZmZmZmZmZmZm Z ddl m Z m Z m Z mZmZmZmZddlmZmZmZddlmZmZddlmZddlmZmZmZmZm Z m!Z!m"Z"m#Z#m$Z$m%Z%ddl&m'Z'm(Z(m)Z)dd l*m+Z+m,Z,d d d gZ-Gd d d e)e)dZ.Gdd d e)e)dZ/dZ0e eefe1dddZ2e3e eefee4e edee5ffdddZ6Gdd d Z7dS)) AnyCallablecastDictListOptionalTupleTypeUnion)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_DATAPAUSEDc@s eZdZdS)r)N)__name__ __module__ __qualname__r.r.c/var/www/downstreamdata.science/rtclock/rtclock-venv/lib/python3.7/site-packages/h11/_connection.pyr)(s) metaclassc@s eZdZdS)r*N)r+r,r-r.r.r.r/r*,si@)eventreturncCs0t|jd}d|krdSt|dddkr,dSdS)Ns connectionscloseF http_versions1.1T)rheadersgetattr)r1 connectionr.r.r/ _keep_aliveHs  r7r.)request_methodr1r2cCst|ttfkstt|tkrf|jdksT|dksT|dkrXd|jkrPdkrXnndS|jdksftt|jd}|r|dgkstd St|jd }|rd t|d ffSt|tkrdSd SdS)N)i0sHEADsCONNECTi,)zcontent-length)rstransfer-encodingschunked)chunkedr.scontent-lengthzcontent-lengthr)zhttp/1.0r.)typerrAssertionError status_coderr4int)r8r1Ztransfer_encodingsZcontent_lengthsr.r.r/ _body_framingQs"  "   r@c@seZdZdZefeeeddddZe e eeeefdddZ e eedd d Z e eedd d Z e edd dZddddZeeddddZeeeedddZeeeddddZeeeeeeefeedefdddZd3e eeeefeedddd Ze eeefdd!d"Zedd#d$d%Z eeee!ee"fdd&d'Z#eeee!ee"fdd(d)Z$eeedd*d+Z%eee&edd,d-Z'ddd.d/Z(e)e)d0d1d2Z*dS)4r(aBAn 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`. N)our_rolemax_incomplete_event_sizer2cCs||_|ttfkr td|||_||tkr:t|_nt|_t|_| |jdt |_ | |jdt |_ t|_d|_d|_d|_d|_dS)Nz#expected CLIENT or SERVER, not {!r}F)_max_incomplete_event_sizerr! ValueErrorformatrA their_roler_cstate_get_io_objectr&_writerr_readerr_receive_buffer_receive_buffer_closedtheir_http_version_request_method"client_is_waiting_for_100_continue)selfrArBr.r.r/__init__s  zConnection.__init__)r2cCs t|jjS)zA dictionary like:: {CLIENT: , SERVER: } See :ref:`state-machine` for details. )dictrGstates)rPr.r.r/rSs zConnection.statescCs|jj|jS)zjThe current state of whichever role we are playing. See :ref:`state-machine` for details. )rGrSrA)rPr.r.r/ our_stateszConnection.our_statecCs|jj|jS)znThe current state of whichever role we are NOT playing. See :ref:`state-machine` for details. )rGrSrF)rPr.r.r/ their_stateszConnection.their_statecCs|jtko|jS)N)rFrrO)rPr.r.r/!they_are_waiting_for_100_continuesz,Connection.they_are_waiting_for_100_continuecCs4t|jj}|jd|_|jr&t||dS)aAttempt 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)rRrGrSstart_next_cyclerNrOr=_respond_to_state_changes)rP old_statesr.r.r/rWs   zConnection.start_next_cycle)roler2cCs&t|jj}|j|||dS)N)rRrGrSZ process_errorrX)rPrZrYr.r.r/_process_errors  zConnection._process_error)r1r2cCsTt|tkr|jdkrtSt|tkrPt|jjkrPd|jkrHdkrPnntSdS)Ner:i,)r<rr>rrrrGZpending_switch_proposals)rPr1r.r.r/_server_switch_events  zConnection._server_switch_event)rZr1r2cCs\t|jj}|tkrNt|tkrN|jdkr6|jtt |j drN|jt d}|t krd| |}|j|t||t|tkr|j|_||jkrt|tttfkrtttttf|}|j|_t|ttfkrtttttf|s|jt|tkrt|rd|_t|ttfkr*d|_|tkrLt|ttfkrLd|_|||dS)NsCONNECTsupgradeTF)rRrGrSrr<rmethodZprocess_client_switch_proposalrrr4rr!r]Z process_eventrNrFrrrr r3rMr7Zprocess_keep_alive_disabledrrOr rrX)rPrZr1rYZserver_switch_eventr.r.r/_process_events8        zConnection._process_event.)rZr1io_dictr2cCsZ|jj|}|tkrHttt|jtttt f|\}}|t||S| ||fSdS)N) rGrSr r@rbytesrNr rrget)rPrZr1r`state framing_typeargsr.r.r/rH4s  "zConnection._get_io_object)rYr1r2cCsH|j||jkr"||j|t|_|j||jkrD||j|t|_dS)N) rTrArHr&rIrUrFrrJ)rPrYr1r.r.r/rXJsz$Connection._respond_to_state_changescCst|j|jfS)abData 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. )rarKrL)rPr.r.r/ trailing_dataUs zConnection.trailing_data)datar2cCs,|r"|jrtd|j|7_nd|_dS)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)rL RuntimeErrorrK)rPrgr.r.r/ receive_data`s 'zConnection.receive_datacCs|j}|tkr|jrtS|tks(|tkr,tS|jdk s:t||j}|dkrx|jsx|jrxt |jdrr|j }nt }|dkrt }|S)Nread_eof) rUrrKr*rr"rJr=rLhasattrrjr r))rPrcr1r.r.r/_extract_next_receive_events    z&Connection._extract_next_receive_eventc Cs|jtkrtdy^|}|ttgkr<||jtt ||tkrnt |j |j kr`tddd|j rntd|Stk r}z&||jt|tr|nWdd}~XYnXdS)aFParse 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)rUrr$rlr)r*r_rFrrlenrKrCrL BaseExceptionr[ isinstancer#Z!_reraise_as_remote_protocol_error)rPr1excr.r.r/ next_events$(      zConnection.next_eventcCs$||}|dkrdSd|SdS)aConvert 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. N)send_with_data_passthroughjoin)rPr1 data_listr.r.r/sends zConnection.sendcCs|jtkrtdy^t|tkr*||}|j}||j|t|t krNdS|dk sZt g}|||j |SWn| |jYnXdS)ahIdentical 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) rTrr#r<r&_clean_up_response_headers_for_sendingrIr_rAr r=appendr[)rPr1writerrur.r.r/rss        z%Connection.send_with_data_passthroughcCs||jdS)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[rA)rPr.r.r/ send_failed'szConnection.send_failed)responser2cCst|tkst|j}d}tt|j}|dkr2d}t||\}}|dkrt|dg}|j dksh|j dkrt|dg}|jdkrd}nt|dd g}|j j r|rt t |d }|d |d t|d t|}t||j|j|jd S)NFsHEADsGET)r;zhttp/1.0scontent-lengths1.1stransfer-encodingTschunkeds connections keep-alivesclose)r4r>r3reason)r<rr=r4rrarNr@rrMrG keep_alivesetrdiscardaddsortedr>r3r|)rPr{r4Z need_closeZmethod_for_choosing_headersrd_r6r.r.r/rw@s0       z1Connection._clean_up_response_headers_for_sending)N)+r+r,r-__doc__!DEFAULT_MAX_INCOMPLETE_EVENT_SIZEr r%r?rQpropertyrrSrTrUboolrVrWr[rrr]r_r rr'rrrHrXrrarfrir)r*rlrqrvrrsrzrrwr.r.r.r/r(s< #  2  0  A!N)8typingrrrrrrrr r Z_eventsr r rrrrr_headersrrr_readersrrZ_receivebufferr_staterrrrrrrr r!r"Z_utilr#r$r%_writersr&r'__all__r)r*rrr7rastrr?r@r(r.r.r.r/s,$  0   &8