98d85677ba
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>
22 lines
768 B
Markdown
22 lines
768 B
Markdown
# Unreleased
|
|
|
|
## Added
|
|
|
|
- Implemented `Eq` for `common::headers::Encoding`, `common::headers::MediaType`,
|
|
`common::headers::Headers`, `common::HttpHeaderError`, `common::Body`, `common::Version`,
|
|
`common::RequestError`, `request::Uri`, `request::RequestLine`, `response::StatusCode`,
|
|
`response::ResponseHeaders`
|
|
- Allowed to set custom headers in HTTP responses.
|
|
|
|
## Changed
|
|
|
|
- Mark `HttpServer::new_from_fd` as `unsafe` as the correctness of the unsafe code
|
|
in this method relies on an invariant the caller has to uphold
|
|
- Always set 'Content-Length' in non-100/204 responses regardless of whether the
|
|
body is empty. Otherwise, the client waits for the server to close the
|
|
connection or for timeout to occur.
|
|
|
|
# v0.1.0
|
|
|
|
- micro-http v0.1.0 first release.
|