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.6-5 Keyword: MUST NOT A client that sends a "close" connection option MUST NOT send further requests on that connection (after the one containing the "close")...

HTTP/1.1
RFC9112
MUST NOT

**RFC 9112 Requirement** Section: 9.6-1 Keyword: SHOULD The "close" connection option is defined as a signal that the sender will close this connection after completion of the response. A sender...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.5-5 Keyword: SHOULD A client sending a message body SHOULD monitor the network connection for an error response while it is transmitting the request. If the...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.5-5 Keyword: SHOULD A client sending a message body SHOULD monitor the network connection for an error response while it is transmitting the request. If the...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.5-4 Keyword: SHOULD A server SHOULD sustain persistent connections, when possible, and allow the underlying transport's flow-control mechanisms to resolve temporary overloads rather than terminate connections...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.5-3 Keyword: MAY A client, server, or proxy MAY close the transport connection at any time. For example, a client might have started to send a...

HTTP/1.1
RFC9112
MAY

**RFC 9112 Requirement** Section: 9.5-2 Keyword: SHOULD A client or server that wishes to time out SHOULD issue a graceful close on the connection. Implementations SHOULD constantly monitor open connections...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.5-2 Keyword: SHOULD A client or server that wishes to time out SHOULD issue a graceful close on the connection. Implementations SHOULD constantly monitor open connections...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.3.2-4 Keyword: SHOULD An intermediary that receives pipelined requests SHOULD pipeline those requests when forwarding them inbound, since it can rely on the outbound user agent(s)...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.3.2-4 Keyword: MAY An intermediary that receives pipelined requests MAY pipeline those requests when forwarding them inbound, since it can rely on the outbound user agent(s)...

HTTP/1.1
RFC9112
MAY