http
http copied to clipboard
Rust HTTP types
Are there plans for this? Would like to use it in constant generics. https://github.com/hyperium/http/blob/bda93204b3da1a776cf471ed39e8e374cec652e7/src/status.rs#L119-L121 Change to this: ```rust pub const fn as_u16(&self) -> u16 { (*self).0.get() } ```
Currently, the `http` crate contains a `HeaderName` type that is used in the implementation of `HeaderMap` as the key type. This `HeaderName` type stores all header names as lower case...
Hello, what is the suggested way to handle a mix of crates using `1.0` and `0.2` versions of _http_? Would it be possible to release a new `0.2.x` version using...
## Present State Currently: [status.rs lines 456 to 458](https://github.com/hyperium/http/blob/bda93204b3da1a776cf471ed39e8e374cec652e7/src/status.rs#L456): ```rust /// 422 Unprocessable Entity /// [[RFC4918](https://tools.ietf.org/html/rfc4918)] (422, UNPROCESSABLE_ENTITY, "Unprocessable Entity"); ``` ## Recommendation Use this instead: ```rust /// 422 Unprocessable...
Closes #529
Since sensitive data can be stored in headers (i.e. credentials in an `Authorization` header), it would be nice for the value to be "zero-ed out" when they are dropped so...
We have `HeaderValue::from_maybe_shared` to create `HeaderValue` from `Bytes` without copying, so what about the reverse?
Hi! An almost complete rust newbie here (coming from C++, mostly), so please forgive my ignorance. ---- I believe it's a pretty common practice to have some company-wide standard headers...
Aims to resolve https://github.com/hyperium/http/issues/653
RFC9110 changed phrases for status code 413 and 422: * 413 Payload Too Large → Content Too Large * 422 Unprocessable Entity → Unprocessable Content Introduce CONTENT_TOO_LARGE and UNPROCESSABLE_CONTENT StatusCode...