lightbug_http
lightbug_http copied to clipboard
saviorand
Simple and fast HTTP framework for Mojo! 🔥
**RFC 9112 Requirement** Section: 6.3-6 Keyword: SHOULD Unless a transfer coding other than chunked has been applied, a client that sends a request containing a message body SHOULD use a...
**RFC 9112 Requirement** Section: 6.3-5 Keyword: MAY A server MAY reject a request that contains a message body but not a Content-Length by responding with 411 (Length Required).¶ Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-6.3-5
**RFC 9112 Requirement** Section: 6.3-3 Keyword: SHOULD Since there is no way to distinguish a successfully completed, close-delimited response message from a partially received message interrupted by network failure, a...
**RFC 9112 Requirement** Section: 6.3-2.4.3 Keyword: MUST If a Transfer-Encoding header field is present in a request and the chunked transfer coding is not the final encoding, the message body...
**RFC 9112 Requirement** Section: 6.2-2 Keyword: MUST NOT A sender MUST NOT send a Content-Length header field in any message that contains a Transfer-Encoding header field.¶ Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-6.2-2
**RFC 9112 Requirement** Section: 6.1-16 Keyword: MUST A server or client that receives an HTTP/1.0 message containing a Transfer-Encoding header field MUST treat the message as if the framing is...
**RFC 9112 Requirement** Section: 6.1-15 Keyword: MUST A server MUST reject a request that contains both Content-Length and Transfer-Encoding or process such a request in accordance with the Transfer-Encoding alone....
**RFC 9112 Requirement** Section: 6.1-15 Keyword: MAY A server MAY reject a request that contains both Content-Length and Transfer-Encoding or process such a request in accordance with the Transfer-Encoding alone....
**RFC 9112 Requirement** Section: 6.1-13 Keyword: MUST NOT A client MUST NOT send a request containing Transfer-Encoding unless it knows the server will handle HTTP/1.1 requests (or later minor revisions);...
**RFC 9112 Requirement** Section: 6.1-13 Keyword: MUST NOT A client MUST NOT send a request containing Transfer-Encoding unless it knows the server will handle HTTP/1.1 requests (or later minor revisions);...