Increase/Decrease status code ranges

Thank you for all the development.

I have seen in h11/h11/_events.py / the handled status codes ranges are between [200, 600).

@dataclass(init=False, frozen=True)
class Response(_ResponseBase):
    """The 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 <headers-format>` 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
       <http_version-format>` for details.
    .. attribute:: reason
       The reason phrase of this response, as a byte string. For example:
       ``b"OK"``, or ``b"Not Found"``.
    """

    def __post_init__(self) -> None:
        if not (200 <= self.status_code < 600):
            raise LocalProtocolError(
                "Response status_code should be in range [200, 600), not {}".format(
                    self.status_code
                )
            )

As this is the standard to follow, it’s great to have it, but there are some http servers that don’t follow the standard. What you think about adding the possibility to setup the status code ranges or increasing them for possible exceptional cases?

[njsmith]

@tyteen4a03 ah, that’s because h11 models 1xx status codes as InformationalResponse objects, not Response objects, because they act in a special way in the HTTP/1.1 state machine.

[SariNusier]

Hi all,

I’m wondering if at least we can include status code 100 because I’m not too sure how else to handle an expect: 100-continue request if we can’t return a repsonse with status code 100.

This is part of the http1.1 protocol [1] as far as I understand it, so do you think it’s valid to add it? Starlette also has this as a return code [2], but if I try to respond with it, I get an exception thrown from h11.

Edit: I just noticed that h11 does support InformationalResponse, so maybe this is a a problem in uvicorn rather than h11 🤔.

Any opinions/suggestions? Thanks!

[1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.2.3 [2] https://github.com/encode/starlette/blob/master/starlette/status.py#L8