o h(.@svddlZddlmZddlmZmZddlmZmZm Z m Z m Z m Z ddl mZmZddlmZmZddlmZmZmZgd Zeed Zeed ZGd d d eZed ddGdddeZed ddGdddeZed ddGdddeZed ddGdddeZ ed ddGdddeZ!ed ddGdddeZ"eddGdddeZ#dS)N)ABC) dataclassfield)AnycastDictListTupleUnion)methodrequest_target)Headersnormalize_and_validate)bytesifyLocalProtocolErrorvalidate)EventRequestInformationalResponseResponseData EndOfMessageConnectionClosedasciic@seZdZdZdZdS)rz$ Base class for h11 events. N)__name__ __module__ __qualname____doc__ __slots__rrr_/var/www/html/construction_image-detection-poc/venv/lib/python3.10/site-packages/h11/_events.pyr srFT)initfrozenc seZdZUdZdZeed<eed<eed<eed<ddd deee fdeee e eefe e e e ffdeee fdeee fd e d d f fd dZ d ZZS)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. )r headerstarget http_versionr r$r%r&1.1F)r&_parsedr(returnNc stt|trt|d|n t|dt||d|s;t|dt|t|dt|t|dt|nt|d|t|d|t|d|d}|jD] \}}|dkra|d7}qU|j d kro|dkrot d |dkrwt d t t |j d t t|jd dS)Nr$r(r r%r&rshostr r'zMissing mandatory Host: headerzFound multiple Host: headerszIllegal method characterszIllegal target characters)super__init__ isinstancerobject __setattr__rrr$r&rr method_rer request_target_rer%) selfr r$r%r&r( host_countnamevalue __class__rr!r,Rs0 zRequest.__init__)rrrrr bytes__annotations__rr strrr boolr,__hash__ __classcell__rrr6r!r(s. ! $   +rc seZdZUdZeed<eed<eed<eed<dddd deee e eefe e e e ffdedeee fdeee fd e d d f fd dZ dddZd ZZS) _ResponseBase)r$r&reason status_coder$r&r?r@r'F)r&r?r(r(r)Ncstt|trt|d|n t|dt||d|sDt|dt|t|dt|t|ts:t dt|dt|nt|d|t|d|t|d|| dS)Nr$r*r?r&zstatus code must be integerr@) r+r,r-rr.r/rrintr __post_init__)r2r$r@r&r?r(r6rr!r,s   z_ResponseBase.__init__cCsdS)Nrr2rrr!rCsz_ResponseBase.__post_init__r)N)rrrr rr9r8rBr rr r:r;r,rCr<r=rrr6r!r>s0 $    r>c@eZdZdZdddZdZdS)raAn 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"``. r)NcC,d|jkr dksntd|jdS)NdzGInformationalResponse status_code should be in range [100, 200), not {}r@rformatrDrrr!rCs z#InformationalResponse.__post_init__rErrrrrCr<rrrr!rs rc@rF)raThe 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, 1000). .. 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"``. r)NcCrG)NrIiz;Response status_code should be in range [200, 1000), not {}rJrDrrr!rCszResponse.__post_init__rErLrrrr!rs  rc @sPeZdZUdZdZeed<eed<eed< d dedededdfd d ZdZ dS) raPart 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_endrMrNrOFr)NcCs.t|d|t|d|t|d|dS)NrMrNrO)r.r/)r2rMrNrOrrr!r,+sz Data.__init__)FF) rrrrr r8r9r;r,r<rrrr!rs"   rc sleZdZUdZdZeed<ddddeeee e e fee e e fdfde ddffd d Z dZZS) rajThe 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. )r$r$NF)r$r(r(r)csDt|durtg}n t|tst||d}t|d|dS)Nr*r$)r+r,rr-rr.r/)r2r$r(r6rr!r,Qs    zEndOfMessage.__init__)rrrrr rr9r rr r8r:r;r,r<r=rrr6r!r;s " r)r#c@seZdZdZdS)raAThis 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)rrrrrrrr!res r)$reabcr dataclassesrrtypingrrrrr r _abnfr r _headersrr_utilrrr__all__compileencoder0r1rrr>rrrrrrrrr!s2     W . ) ) 7)