U ʼba@sddlTddlTddlmZmZmZddlmZmZmZddl m Z m Z m Z ddl mZddlmZddlmZdd d gZed Zed Zd Zd d ZddZGdddeZdS))*)LocalProtocolErrorRemoteProtocolError make_sentinel)ConnectionState_SWITCH_UPGRADE_SWITCH_CONNECT)get_comma_headerset_comma_headerhas_expect_100_continue) ReceiveBuffer)READERS)WRITERS Connection NEED_DATAPAUSEDi@cCs0t|jd}d|krdSt|dddkr,dSdS)N connectioncloseF http_version1.1T)r headersgetattr)event connectionr3/tmp/pip-unpacked-wheel-rko__zic/h11/_connection.py _keep_alive0s  rcCst|ttfkstt|tkrf|jdksT|dksT|dkrXd|jkrPdkrXnndS|jdksftt|jd}|r|dgkstd St|jd }|rd t|d ffSt|tkrdSd SdS)N)i0HEADCONNECT,)content-length)transfer-encodingschunked)chunkedrcontent-lengthr"r#)http/1.0r)typeRequestResponseAssertionError status_coder rint)request_methodrZtransfer_encodingsZcontent_lengthsrrr _body_framing8s0      r/c@seZdZdZefddZeddZeddZedd Z ed d Z d d Z ddZ ddZ ddZddZd)ddZeddZddZddZdd Zd!d"Zd#d$Zd%d&Zd'd(ZdS)*raBAn 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`. cCs||_|ttfkr td|||_|tkr6t|_nt|_t|_| |jdt |_ | |jdt |_ t|_d|_d|_d|_d|_dS)Nz#expected CLIENT or SERVER, not {!r}F)_max_incomplete_event_sizeCLIENTSERVER ValueErrorformatour_role their_roler_cstate_get_io_objectr_writerr _readerr _receive_buffer_receive_buffer_closedtheir_http_version_request_method"client_is_waiting_for_100_continue)selfr5Zmax_incomplete_event_sizerrr__init__|s" zConnection.__init__cCs t|jjS)zA dictionary like:: {CLIENT: , SERVER: } See :ref:`state-machine` for details. )dictr7statesr@rrrrCs zConnection.statescCs|jj|jS)zjThe current state of whichever role we are playing. See :ref:`state-machine` for details. )r7rCr5rDrrr our_stateszConnection.our_statecCs|jj|jS)znThe current state of whichever role we are NOT playing. See :ref:`state-machine` for details. )r7rCr6rDrrr their_stateszConnection.their_statecCs|jtko|jSN)r6r1r?rDrrr!they_are_waiting_for_100_continues z,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)rBr7rCstart_next_cycler>r?r+_respond_to_state_changes)r@ old_statesrrrrIs   zConnection.start_next_cyclecCs&t|jj}|j|||dSrG)rBr7rCZ process_errorrJ)r@rolerKrrr_process_errors  zConnection._process_errorcCsTt|tkr|jdkrtSt|tkrPt|jjkrPd|jkrHdkrPnntSdS)Ner r!)r(InformationalResponser,rr*rr7Zpending_switch_proposals)r@rrrr_server_switch_events   zConnection._server_switch_eventcCs6t|jj}|tkrNt|tkrN|jdkr6|jtt |j drN|jt d}|t krd| |}|j|t||t|tkr|j|_||jkrt|tttfkr|j|_t|ttfkrt|s|jt|tkrt|rd|_t|ttfkrd|_|tkr&t|ttfkr&d|_|||dS)NrsupgradeTF)rBr7rCr1r(r)methodZprocess_client_switch_proposalrr rrr2rPZ process_eventr>r6r*rOrr=rZprocess_keep_alive_disabledr r?DataZ EndOfMessagerJ)r@rLrrKZserver_switch_eventrrr_process_events2         zConnection._process_eventcCsF|jj|}|tkr4t|j|\}}|t||S|||fSdSrG)r7rCZ SEND_BODYr/r>get)r@rLrZio_dictstate framing_typeargsrrrr8s  zConnection._get_io_objectNcCsH|j||jkr"||j|t|_|j||jkrD||j|t|_dSrG) rEr5r8rr9rFr6r r:)r@rKrrrrrJsz$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. )bytesr;r<rDrrr trailing_data$s zConnection.trailing_datacCs,|r"|jrtd|j|7_nd|_dS)aAdd data to our internal recieve 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)r< RuntimeErrorr;)r@datarrr 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) rFZDONEr;rZMIGHT_SWITCH_PROTOCOLZSWITCHED_PROTOCOLr:r+r<hasattrr]ConnectionClosedr)r@rUrrrr_extract_next_receive_event^s    z&Connection._extract_next_receive_eventc Cs|jtkrtdzd|}|ttfkr@||j||j |tkrrt |j|j krdtddd|j rrtd|WSt k r}z&||jt|tr|nW5d}~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)rFERRORrr`rrrSr6r;compresslenr0r< BaseExceptionrM isinstancerZ!_reraise_as_remote_protocol_error)r@rexcrrr next_eventxs0(      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)r@r data_listrrrsends zConnection.sendcCs|jtkrtdzbt|tkr*|||j}||j|t|t krPWdS|dk s\t g}|||j |WSWn| |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) rErarr(r*&_clean_up_response_headers_for_sendingr9rSr5r_r+appendrM)r@rwriterrkrrrris$        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)rMr5rDrrr send_failedszConnection.send_failedcCst|tkstt|j}d}|j}|dkr0d}t||\}}|dkrt|dg|jdksf|jdkrt|dg|jdkrd}nt|dd g|j j r|rt t |d }| d |d t|d t|||_dS) NFrsGET)r%r'r&rr$Tr%rs keep-aliver)r(r*r+listrr>r/r r=r7 keep_alivesetr discardaddsorted)r@responserZ need_closeZmethod_for_choosing_headersrV_rrrrrms,         z1Connection._clean_up_response_headers_for_sending)N)__name__ __module__ __qualname____doc__!DEFAULT_MAX_INCOMPLETE_EVENT_SIZErApropertyrCrErFrHrIrMrPrSr8rJrYr\r`rgrlrirprmrrrrrms4 %     ,  /C"N)Z_events_stateZ_utilrrrrrr_headersr r r Z_receivebufferr _readersr _writersr__all__rrr}rr/objectrrrrrs     5