Go to file

Takahiro Itazuri 98d85677ba feat: Allow to set custom headers in response

EC2 IMDS includes X-Aws-Ec2-Metadata-Token-Ttl-Seconds header in the
response to PUT /latest/api/token. To enable Firecracker MMDS to behave
compatibly with EC2 IMDS, allow to set custom headers in HTTP response.

Signed-off-by: Takahiro Itazuri <itazur@amazon.com>

2025-07-23 11:13:45 +01:00

.cargo

fix link issues on aarch64 musl

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

.github

Dependabot

2023-09-20 14:13:56 +01:00

rust-vmm-ci @ aa2f8a90e4

Bump rust-vmm-ci from c3ef897 to aa2f8a9

2025-07-02 09:45:47 +02:00

src

feat: Allow to set custom headers in response

2025-07-23 11:13:45 +01: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

Update vmm-sys-util to 0.12.0

2024-01-02 17:07:08 +00:00

Cargo.toml

chore: update vmm-sys-util to 0.14.0

2025-05-30 17:15:01 +02:00

CHANGELOG.md

feat: Allow to set custom headers in response

2025-07-23 11:13:45 +01:00

CONTRIBUTING.md

added contribution guidelines

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

coverage_config_aarch64.json

chore(coverage): adjusted coverage

2023-08-24 17:56:59 +01:00

coverage_config_x86_64.json

chore: update coverage

2025-01-14 12:31:04 +00: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.