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.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

**RFC 9112 Requirement** Section: 9.3.2-3 Keyword: SHOULD NOT Idempotent methods (Section 9.2.2 of [HTTP]) are significant to pipelining because they can be automatically retried after a connection failure. A user...

HTTP/1.1
RFC9112
SHOULD NOT

**RFC 9112 Requirement** Section: 9.3.2-2 Keyword: MUST NOT A client that pipelines requests MUST NOT retry unanswered requests if the connection closes before it receives all of the corresponding responses....

HTTP/1.1
RFC9112
MUST NOT

**RFC 9112 Requirement** Section: 9.3.2-2 Keyword: SHOULD A client that pipelines requests SHOULD retry unanswered requests if the connection closes before it receives all of the corresponding responses. When retrying...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 9.3.2-1 Keyword: MUST A client that supports persistent connections MUST "pipeline" its requests (i.e., send multiple requests without waiting for each response). A server MAY process...

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 9.3.2-1 Keyword: MAY A client that supports persistent connections MAY "pipeline" its requests (i.e., send multiple requests without waiting for each response). A server MAY process...

HTTP/1.1
RFC9112
MAY

**RFC 9112 Requirement** Section: 9.3.2-1 Keyword: MAY A client that supports persistent connections MAY "pipeline" its requests (i.e., send multiple requests without waiting for each response). A server MAY process...

HTTP/1.1
RFC9112
MAY

**RFC 9112 Requirement** Section: 9.3-8 Keyword: MUST NOT A proxy server MUST NOT maintain a persistent connection with an HTTP/1.0 client (see Appendix C.2.2 for information and discussion of the...

HTTP/1.1
RFC9112
MUST NOT

**RFC 9112 Requirement** Section: 9.3-7 Keyword: MUST In order to remain persistent, all messages on a connection need to have a self-defined message length (i.e., one not defined by closure...

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 9.3-7 Keyword: MUST In order to remain persistent, all messages on a connection need to have a self-defined message length (i.e., one not defined by closure...

HTTP/1.1
RFC9112
MUST