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: 7.4-8 Keyword: MUST Since the TE header field only applies to the immediate connection, a sender of TE MUST also send a "TE" connection option within...

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 7.4-5 Keyword: MAY When multiple transfer codings are acceptable, the client MAY rank the codings by preference using a case-insensitive "q" parameter (similar to the qvalues...

HTTP/1.1
RFC9112
MAY

**RFC 9112 Requirement** Section: 7.4-2 Keyword: MUST NOT A client MUST NOT send the chunked transfer coding name in TE; chunked is always acceptable for HTTP/1.1 recipients.¶ Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-7.4-2

HTTP/1.1
RFC9112
MUST NOT

**RFC 9112 Requirement** Section: 7.3-6 Keyword: MUST Values to be added to this namespace require IETF Review (see Section 4.8 of [RFC8126]) and MUST conform to the purpose of transfer...

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 7.3-5 Keyword: SHOULD NOT The TE header field (Section 10.1.4 of [HTTP]) uses a pseudo-parameter named "q" as the rank value when multiple transfer codings are...

HTTP/1.1
RFC9112
SHOULD NOT

**RFC 9112 Requirement** Section: 7.3-4 Keyword: MUST NOT Names of transfer codings MUST NOT overlap with names of content codings (Section 8.4.1 of [HTTP]) unless the encoding transformation is identical,...

HTTP/1.1
RFC9112
MUST NOT

**RFC 9112 Requirement** Section: 7.3-2 Keyword: MUST Registrations MUST include the following fields:¶ Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-7.3-2

HTTP/1.1
RFC9112
MUST

**RFC 9112 Requirement** Section: 7.2-3 Keyword: SHOULD The compression codings do not define any parameters. The presence of parameters with any of these compression codings SHOULD be treated as an...

HTTP/1.1
RFC9112
SHOULD

**RFC 9112 Requirement** Section: 7.1.2-3 Keyword: MUST NOT A recipient that removes the chunked coding from a message MUST NOT selectively retain or discard the received trailer fields. A recipient...

HTTP/1.1
RFC9112
MUST NOT

**RFC 9112 Requirement** Section: 7.1.2-3 Keyword: MUST A recipient that removes the chunked coding from a message MUST selectively retain or discard the received trailer fields. A recipient that retains...

HTTP/1.1
RFC9112
MUST