Skip to content

Issues: Lightbug-HQ/lightbug_http

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

145 Open 24 Closed
145 Open 24 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

[10.1-1] MUST: The "message/http" media type can be used to enclose a single HTTP request or response message, prov... HTTP/1.1 HTTP/1.1 specification MUST Mandatory requirement RFC9112 RFC 9112 requirements
#234 opened Jan 15, 2025 by saviorand
[9.8-10] MAY: Servers MAY attempt to initiate an exchange of closure alerts with the client before closing the con... HTTP/1.1 HTTP/1.1 specification MAY Optional requirement RFC9112 RFC 9112 requirements
#233 opened Jan 15, 2025 by saviorand
[9.8-10] MUST: Servers MUST attempt to initiate an exchange of closure alerts with the client before closing the co... HTTP/1.1 HTTP/1.1 specification MUST Mandatory requirement RFC9112 RFC 9112 requirements
#232 opened Jan 15, 2025 by saviorand
[9.8-9] SHOULD: Servers SHOULD be prepared to receive an incomplete close from the client, since the client can ofte... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#231 opened Jan 15, 2025 by saviorand
[9.8-8] MAY: Clients MAY send a closure alert before closing the connection. Clients that do not expect to receiv... HTTP/1.1 HTTP/1.1 specification MAY Optional requirement RFC9112 RFC 9112 requirements
#230 opened Jan 15, 2025 by saviorand
[9.8-8] MUST: Clients MUST send a closure alert before closing the connection. Clients that do not expect to recei... HTTP/1.1 HTTP/1.1 specification MUST Mandatory requirement RFC9112 RFC 9112 requirements
#229 opened Jan 15, 2025 by saviorand
[9.8-7] SHOULD: A client detecting an incomplete close SHOULD recover gracefully.¶... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#228 opened Jan 15, 2025 by saviorand
[9.8-4] SHOULD: When encountering an incomplete close, a client SHOULD treat as completed all requests for which it ... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#227 opened Jan 15, 2025 by saviorand
[9.7-2] MUST: The HTTP client also acts as the TLS client. It initiates a connection to the server on the appropri... HTTP/1.1 HTTP/1.1 specification MUST Mandatory requirement RFC9112 RFC 9112 requirements
#226 opened Jan 15, 2025 by saviorand
[9.6-8] SHOULD NOT: A client that receives a "close" connection option SHOULD NOT cease sending requests on that connect... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD NOT Recommended prohibition
#225 opened Jan 15, 2025 by saviorand
[9.6-8] MUST: A client that receives a "close" connection option MUST cease sending requests on that connection an... HTTP/1.1 HTTP/1.1 specification MUST Mandatory requirement RFC9112 RFC 9112 requirements
#224 opened Jan 15, 2025 by saviorand
[9.6-7] MUST NOT: A server that sends a "close" connection option MUST NOT initiate closure of the connection (see bel... HTTP/1.1 HTTP/1.1 specification MUST NOT Mandatory prohibition RFC9112 RFC 9112 requirements
#223 opened Jan 15, 2025 by saviorand
[9.6-7] MUST: A server that sends a "close" connection option MUST initiate closure of the connection (see below) ... HTTP/1.1 HTTP/1.1 specification MUST Mandatory requirement RFC9112 RFC 9112 requirements
#222 opened Jan 15, 2025 by saviorand
[9.6-6] MUST NOT: A server that receives a "close" connection option MUST NOT initiate closure of the connection (see ... HTTP/1.1 HTTP/1.1 specification MUST NOT Mandatory prohibition RFC9112 RFC 9112 requirements
#221 opened Jan 15, 2025 by saviorand
[9.6-6] SHOULD: A server that receives a "close" connection option SHOULD initiate closure of the connection (see be... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#220 opened Jan 15, 2025 by saviorand
[9.6-6] MUST: A server that receives a "close" connection option MUST initiate closure of the connection (see belo... HTTP/1.1 HTTP/1.1 specification MUST Mandatory requirement RFC9112 RFC 9112 requirements
#219 opened Jan 15, 2025 by saviorand
[9.6-5] MUST: A client that sends a "close" connection option MUST send further requests on that connection (after... HTTP/1.1 HTTP/1.1 specification MUST Mandatory requirement RFC9112 RFC 9112 requirements
#218 opened Jan 15, 2025 by saviorand
[9.6-5] MUST NOT: A client that sends a "close" connection option MUST NOT send further requests on that connection (a... HTTP/1.1 HTTP/1.1 specification MUST NOT Mandatory prohibition RFC9112 RFC 9112 requirements
#217 opened Jan 15, 2025 by saviorand
[9.6-1] SHOULD: The "close" connection option is defined as a signal that the sender will close this connection afte... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#216 opened Jan 15, 2025 by saviorand
[9.5-5] SHOULD: A client sending a message body SHOULD monitor the network connection for an error response while it... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#215 opened Jan 15, 2025 by saviorand
[9.5-5] SHOULD: A client sending a message body SHOULD monitor the network connection for an error response while it... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#214 opened Jan 15, 2025 by saviorand
[9.5-4] SHOULD: A server SHOULD sustain persistent connections, when possible, and allow the underlying transport's ... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#213 opened Jan 15, 2025 by saviorand
[9.5-3] MAY: A client, server, or proxy MAY close the transport connection at any time. For example, a client mig... HTTP/1.1 HTTP/1.1 specification MAY Optional requirement RFC9112 RFC 9112 requirements
#212 opened Jan 15, 2025 by saviorand
[9.5-2] SHOULD: A client or server that wishes to time out SHOULD issue a graceful close on the connection. Implemen... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#211 opened Jan 15, 2025 by saviorand
[9.5-2] SHOULD: A client or server that wishes to time out SHOULD issue a graceful close on the connection. Implemen... HTTP/1.1 HTTP/1.1 specification RFC9112 RFC 9112 requirements SHOULD Recommended requirement
#210 opened Jan 15, 2025 by saviorand
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.