lightbug_http icon indicating copy to clipboard operation
lightbug_http copied to clipboard

Simple and fast HTTP framework for Mojo! πŸ”₯

Results 135 lightbug_http issues
Sort by recently updated
recently updated
newest added

**RFC 9112 Requirement** Section: 9.3-6 Keyword: MAY A client MAY send additional requests on a persistent connection until it sends or receives a "close" connection option or receives an HTTP/1.0...

HTTP/1.1
RFC9112
MAY

**RFC 9112 Requirement** Section: 9.3-5 Keyword: MUST A server that does not support persistent connections MUST send the "close" connection option in every response message that does not have a...

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 9.3-4 Keyword: MUST A client that does not support persistent connections MUST send the "close" connection option in every request message.ΒΆ Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-9.3-4

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 9.3-1 Keyword: SHOULD HTTP/1.1 defaults to the use of "persistent connections", allowing multiple requests and responses to be carried over a single connection. HTTP implementations SHOULD...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.2-3 Keyword: SHOULD If a client receives data on a connection that doesn't have outstanding requests, the client SHOULD consider that data to be a valid...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.2-3 Keyword: MUST NOT If a client receives data on a connection that doesn't have outstanding requests, the client MUST NOT consider that data to be...

HTTP/1.1
RFC9112
MUST NOT

**RFC 9112 Requirement** Section: 9.2-2 Keyword: MUST A client that has more than one outstanding request on a connection MUST maintain a list of outstanding requests in the order sent...

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 9.2-2 Keyword: MUST A client that has more than one outstanding request on a connection MUST maintain a list of outstanding requests in the order sent...

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 8-2 Keyword: MUST A client that receives an incomplete response message, which can occur when a connection is closed prematurely or when decoding a supposedly chunked...

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 8-1 Keyword: MAY A server that receives an incomplete request message, usually due to a canceled request or a triggered timeout exception, MAY send an error...

HTTP/1.1
RFC9112
MAY