lightbug_http
lightbug_http copied to clipboard
saviorand
Simple and fast HTTP framework for Mojo! 🔥
**Describe the bug** ``` .magic/envs/default/lib/mojo/lightbug_http.mojopkg:0:0: error: unknown attribute code: 36 src/main.mojo:2:6: error: failed to materialize top-level module from lightbug_http.client import Client ^ src/main.mojo:2:20: error: from lightbug_http.client import Client ^ mojo:...
（Sorry, but I'm new to the Mojo community.） I followed the official Mojo manual for the setup and attempted to install lightbug_http using magic, but it didn't work. Steps to...
gzip and deflate per [RFC 9910](https://www.rfc-editor.org/rfc/rfc9110.html#section-8.4.1.2)
**RFC 9112 Requirement** Section: 10.1-1 Keyword: MUST The "message/http" media type can be used to enclose a single HTTP request or response message, provided that it obeys the MIME restrictions...
**RFC 9112 Requirement** Section: 9.8-10 Keyword: MAY Servers MAY attempt to initiate an exchange of closure alerts with the client before closing the connection. Servers MAY close the connection after...
**RFC 9112 Requirement** Section: 9.8-10 Keyword: MUST Servers MUST attempt to initiate an exchange of closure alerts with the client before closing the connection. Servers MAY close the connection after...
**RFC 9112 Requirement** Section: 9.8-9 Keyword: SHOULD Servers SHOULD be prepared to receive an incomplete close from the client, since the client can often locate the end of server data.¶...
**RFC 9112 Requirement** Section: 9.8-8 Keyword: MAY Clients MAY send a closure alert before closing the connection. Clients that do not expect to receive any more data MAY choose not...
**RFC 9112 Requirement** Section: 9.8-8 Keyword: MUST Clients MUST send a closure alert before closing the connection. Clients that do not expect to receive any more data MAY choose not...
**RFC 9112 Requirement** Section: 9.8-7 Keyword: SHOULD A client detecting an incomplete close SHOULD recover gracefully.¶ Reference: https://www.rfc-editor.org/rfc/rfc9112.html#section-9.8-7