lightbug_http
lightbug_http copied to clipboard
Simple and fast HTTP framework for Mojo! 🔥
**RFC 9112 Requirement** Section: 7.1.2-3 Keyword: MAY A recipient that removes the chunked coding from a message MAY selectively retain or discard the received trailer fields. A recipient that retains...
**RFC 9112 Requirement** Section: 7.1.1-4 Keyword: MUST A recipient MUST ignore unrecognized chunk extensions. A server ought to limit the total length of chunk extensions received in a request to...
**RFC 9112 Requirement** Section: 7.1-6 Keyword: SHOULD The chunked coding does not define any parameters. Their presence SHOULD be treated as an error.¶ Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-7.1-6
**RFC 9112 Requirement** Section: 7.1-5 Keyword: MUST HTTP/1.1 does not define any means to limit the size of a chunked response such that an intermediary can be assured of buffering...
**RFC 9112 Requirement** Section: 7.1-4 Keyword: MUST A recipient MUST be able to parse and decode the chunked transfer coding.¶ Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-7.1-4
**RFC 9112 Requirement** Section: 7.1-1 Keyword: OPTIONAL The chunked transfer coding wraps content in order to transfer it as a series of chunks, each with its own size indicator, followed...
**RFC 9112 Requirement** Section: 6.3-8 Keyword: MUST NOT If the final response to the last request on a connection has been completely received and there remains additional data to read,...
**RFC 9112 Requirement** Section: 6.3-8 Keyword: MAY If the final response to the last request on a connection has been completely received and there remains additional data to read, a...
**RFC 9112 Requirement** Section: 6.3-7 Keyword: MUST NOT A user agent that sends a request that contains a message body MUST NOT send either a valid Content-Length header field or...
**RFC 9112 Requirement** Section: 6.3-7 Keyword: MUST A user agent that sends a request that contains a message body MUST send either a valid Content-Length header field or use the...