o Dh&@sddlZddlmZddlmZddlmZmZmZgdZ e e dZ Gdd d e ZGd d d eZGd d d eZGdddeZGdddeZGdddeZGdddeZGdddeZdS)N)_headers)request_target)bytesifyLocalProtocolErrorvalidate)RequestInformationalResponseResponseData EndOfMessageConnectionClosedasciic@s@eZdZgZiZddZddZddZddZd d Z d Z d S) _EventBundlecKs|dd}t|j}|D]}||vrtd||jjq ||j}|D]}||vr6td||jjq&|j |j|j |d|j vrRt j |j |d|_ |s}dD]}||j vrgt|j ||j |<qVd|j vr}t|jtswtd t|j|_|dS) N_parsedFzunrecognized kwarg {} for {}z missing required kwarg {} for {}headers)r)methodtarget http_versionreason status_codezstatus code must be integer)popset_fields TypeErrorformat __class____name__ difference _defaults__dict__updaternormalize_and_validaterr isinstancerintr _validate)selfkwargsrallowedkwargrequiredfieldr,F/var/www/html/env_mimamsha/lib/python3.10/site-packages/h11/_events.py__init__sF          z_EventBundle.__init__cCsdSNr,r&r,r,r-r%Isz_EventBundle._validatecs2jj}fddjD}d|}d||S)Ncsg|] }d|j|qS)z{}={})rr ).0r+r0r,r- Nsz)_EventBundle.__repr__..z, z{}({}))rrrjoinr)r&name kwarg_strs kwarg_strr,r0r-__repr__Ls    z_EventBundle.__repr__cCs|j|jko |j|jkSr/)rr r&otherr,r,r-__eq__Usz_EventBundle.__eq__cCs || Sr/)r:r8r,r,r-__ne__Xs z_EventBundle.__ne__N) r __module__ __qualname__rrr.r%r7r:r;__hash__r,r,r,r-rs* rc@s(eZdZdZgdZddiZddZdS)ranThe beginning of an HTTP request. Fields: .. attribute:: method An HTTP method, e.g. ``b"GET"`` or ``b"POST"``. Always a byte string. :term:`Bytes-like objects ` and native strings containing only ascii characters will be automatically converted to byte strings. .. attribute:: target The target of an HTTP request, e.g. ``b"/index.html"``, or one of the more exotic formats described in `RFC 7320, section 5.3 `_. Always a byte string. :term:`Bytes-like objects ` and native strings containing only ascii characters will be automatically converted to byte strings. .. attribute:: headers Request headers, represented as a list of (name, value) pairs. See :ref:`the header normalization rules ` for details. .. attribute:: http_version The HTTP protocol version, represented as a byte string like ``b"1.1"``. See :ref:`the HTTP version normalization rules ` for details. )rrrrr1.1cCs`d}|jD] \}}|dkr|d7}q|jdkr|dkrtd|dkr'tdtt|jddS)Nrshostrr?zMissing mandatory Host: headerzFound multiple Host: headerszIllegal target characters)rrrrrequest_target_rer)r& host_countr4valuer,r,r-r%szRequest._validateN)rr<r=__doc__rrr%r,r,r,r-r_s ! rc@seZdZgdZdddZdS) _ResponseBase)rrrrr?)rrN)rr<r=rrr,r,r,r-rDsrDc@eZdZdZddZdS)r aAn HTTP informational response. Fields: .. attribute:: status_code The status code of this response, as an integer. For an :class:`InformationalResponse`, this is always in the range [100, 200). .. attribute:: headers Request headers, represented as a list of (name, value) pairs. See :ref:`the header normalization rules ` for details. .. attribute:: http_version The HTTP protocol version, represented as a byte string like ``b"1.1"``. See :ref:`the HTTP version normalization rules ` for details. .. attribute:: reason The reason phrase of this response, as a byte string. For example: ``b"OK"``, or ``b"Not Found"``. cC,d|jkr dksntd|jdS)NdzGInformationalResponse status_code should be in range [100, 200), not {}rrrr0r,r,r-r%s zInformationalResponse._validateNrr<r=rCr%r,r,r,r-r s r c@rF)r aThe beginning of an HTTP response. Fields: .. attribute:: status_code The status code of this response, as an integer. For an :class:`Response`, this is always in the range [200, 600). .. attribute:: headers Request headers, represented as a list of (name, value) pairs. See :ref:`the header normalization rules ` for details. .. attribute:: http_version The HTTP protocol version, represented as a byte string like ``b"1.1"``. See :ref:`the HTTP version normalization rules ` for details. .. attribute:: reason The reason phrase of this response, as a byte string. For example: ``b"OK"``, or ``b"Not Found"``. cCrG)NrIiXz:Response status_code should be in range [200, 600), not {}rJr0r,r,r-r%szResponse._validateNrKr,r,r,r-r s r c@s"eZdZdZgdZdddZdS)r aPart of an HTTP message body. Fields: .. attribute:: data A :term:`bytes-like object` containing part of a message body. Or, if using the ``combine=False`` argument to :meth:`Connection.send`, then any object that your socket writing code knows what to do with, and for which calling :func:`len` returns the number of bytes that will be written -- see :ref:`sendfile` for details. .. attribute:: chunk_start A marker that indicates whether this data object is from the start of a chunked transfer encoding chunk. This field is ignored when when a Data event is provided to :meth:`Connection.send`: it is only valid on events emitted from :meth:`Connection.next_event`. You probably shouldn't use this attribute at all; see :ref:`chunk-delimiters-are-bad` for details. .. attribute:: chunk_end A marker that indicates whether this data object is the last for a given chunked transfer encoding chunk. This field is ignored when when a Data event is provided to :meth:`Connection.send`: it is only valid on events emitted from :meth:`Connection.next_event`. You probably shouldn't use this attribute at all; see :ref:`chunk-delimiters-are-bad` for details. )data chunk_start chunk_endF)rMrNNrr<r=rCrrr,r,r,r-r s r c@seZdZdZdgZdgiZdS)r ajThe end of an HTTP message. Fields: .. attribute:: headers Default value: ``[]`` Any trailing headers attached to this message, represented as a list of (name, value) pairs. See :ref:`the header normalization rules ` for details. Must be empty unless ``Transfer-Encoding: chunked`` is in use. rNrOr,r,r,r-r s r c@seZdZdZdS)r aAThis event indicates that the sender has closed their outgoing connection. Note that this does not necessarily mean that they can't *receive* further data, because TCP connections are composed to two one-way channels which can be closed independently. See :ref:`closing` for details. No fields. N)rr<r=rCr,r,r,r-r &s r )rer_abnfr_utilrrr__all__compileencoder@objectrrrDr r r r r r,r,r,r-s   D7&&*