hyper
hyper copied to clipboard
hyperium
An HTTP library for Rust
**Version** `v0.14.27` **Platform** `Linux demo 5.15.90.1-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux` Tested on several other linux platforms(ubuntu, debian, etc), same issue occurred. **Description**...
https://github.com/hyperium/hyper/blob/1d4ff3597b8e76818c8553dbfa4234cf4208c958/src/proto/h2/mod.rs#L389C8-L397 This isn't sound. `Neutered` is: ```rust #[repr(transparent)] struct Neutered { _inner: B, impossible: Impossible, } enum Impossible {} ``` Firstly, it's unclear what guarantees `repr(transparent)` confers here, `impossible` does...
Currently, one does not simple create own project based on provided examples because almost all examples depends on internal structure [TokioIo](https://github.com/hyperium/hyper/blob/master/benches/support/tokiort.rs#L92). PS: already found `TokioIo` in `hyper-util` crate. At least,...
**Version** current git master **Platform** Linux **Description** hyper rejects HTTP responses where the first header has leading whitespace. This is spec compliant. The popular browsers accept such headers and therefore...
## Requested functionality When writing an HTTP server with hyper, I want to be able to receive and read the [chunk extensions](https://www.rfc-editor.org/rfc/rfc9112#name-chunk-extensions) that clients send when using HTTP/1.1 chunked encoding....
**Version** current from master **Platform** Linux **Description** I'm using hyper in curl, and when I receive a HTTP/1 response with **many** response headers, hyper cuts off the response and returns...
Uses `non_exhaustive` attribute instead of manual implementation.
Hyper currently depends on both `futures_channel` and `tokio::sync`, using both channel types in different places. To cut down on dependencies one of these should be removed.
**Version** 1.0.1 https://docs.rs/hyper/1.0.1/hyper/client/conn/index.html The link just goes to the module hyper::client above which only contains conn now. Presumably it refers to the code now moved to hyper-util.
**Is your feature request related to a problem? Please describe.** It is impossible to write an implementation of `hyper::rt::Read` because `ReadBufCursor` cannot be written to safely. **Describe the solution you'd...
