Go to file

George Pisaltu 0a58eb1ece added support for Deprecation header

This commit adds support for the `Deprecation` HTTP header based on
https://tools.ietf.org/id/draft-dalal-deprecation-header-03.html .
Users can set this header in a `Response` to send a
"Deprecation: true" header field back to the requester, signaling
that the resource accessed has been deprecated.

Signed-off-by: George Pisaltu <gpl@amazon.com>

2021-10-19 20:37:52 +03: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 @ c309d0627b

Added Buildkite CI

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

src

added support for Deprecation header

2021-10-19 20:37:52 +03: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

Cargo.lock

Clean up after cherry-picking commits from firecracker

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

Cargo.toml

Clean up after cherry-picking commits from firecracker

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

CHANGELOG.md

added a basic changelog file

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

CONTRIBUTING.md

added contribution guidelines

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

coverage_config.json

added support for Deprecation header

2021-10-19 20:37:52 +03:00

LICENSE

added license

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

README.md

added readme file

2020-03-24 18:22:44 +02: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.

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.