Go to file

Patrick Roy 43d5a1d4b0 Clear all clippy warnings

Additionally, HttpServer::new_from_fd has been marked as unsafe,
since the correctness of the unsafe call within the function
relies on the caller upholding an invariant

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>

2022-11-22 12:15:22 +02:00

.cargo

fix link issues on aarch64 musl

2020-01-30 15:21:04 +02:00

.github

added github issue template

2020-03-24 18:22:44 +02:00

rust-vmm-ci @ 7af2e16d91

updated rust-vmm-ci

2022-11-22 12:15:22 +02:00

src

Clear all clippy warnings

2022-11-22 12:15:22 +02:00

.gitignore

add .gitignore file

2020-07-23 18:17:33 +03:00

.gitmodules

Added Buildkite CI

2020-01-30 15:21:04 +02:00

build.rs

Clarifying unix-like support

2022-06-13 09:39:48 +03:00

Cargo.lock

Receive multiple file descriptors with a Request

2022-01-28 19:30:22 +02:00

Cargo.toml

Clean up after cherry-picking commits from firecracker

2021-04-15 11:21:32 +03:00

CHANGELOG.md

Clear all clippy warnings

2022-11-22 12:15:22 +02:00

CONTRIBUTING.md

added contribution guidelines

2020-03-24 18:22:44 +02:00

coverage_config.json

Receive multiple file descriptors with a Request

2022-01-28 19:30:22 +02:00

LICENSE

added license

2020-03-24 18:22:44 +02:00

README.md

Clarifying unix-like support

2022-06-13 09:39:48 +03:00

SECURITY-POLICY.md

added security policy document

2020-03-24 18:22:44 +02:00

README.md

micro-http

This is a minimal implementation of the HTTP/1.0 and HTTP/1.1 protocols. This HTTP implementation is stateless thus it does not support chunking or compression.

The micro-http implementation is used in production by Firecracker.

As micro-http uses std::os::unix this crates only supports Unix-like targets.

Contributing

To contribute to micro-http, checkout the contribution guidelines.

Releases

New micro-http versions are released via the GitHub repository releases page. A history of changes is recorded in our changelog.

Policy for Security Disclosures

If you suspect you have uncovered a vulnerability, contact us privately, as outlined in our security policy document; we will immediately prioritize your disclosure.