async-h1
async-h1 copied to clipboard
Asynchronous HTTP/1.1 in Rust
How can I detect from a handler that the underlying request is canceled? Other server implementations such as `hyper` drop the handle future on request cancelation, but it seems `async-h1`...
As pointed out by @Fishrock123 in https://github.com/http-rs/async-h1/pull/158/files#r530051517, Node.js caches timestamps for a minute, making it much easier to handle requests at a high volume. We should consider adopting this approach...
I'm using [schemathesis](https://github.com/schemathesis/schemathesis) (just the worst name) to run OpenAPI tests against my Tide server. A number of these tests outright fail with connection resets by the server and [obtuse...
As suggested in discord, I think.
Hi there, Please consider this more of a question than a bug report. I am trying to implement a TLS listener with tide, which requires me to implement a ToListener/Listener....
async-h1 depends on `async-std` with the `unstable` feature; that in turn pulls in wasm dependencies via `futures-timer` then `gloo-timers`. Please consider adjusting the feature flag dependencies to avoid pulling `gloo-timers`...
~~I'm pretty sure this will fail with any input, it hanged up while reading header.~~ I forgot to `wake` and it's working now.
An `Error` always has an associated `StatusCode`. From this, I assumed that errors are converted into HTTP responses when using the `accept` function. However, that does not seem to be...
Is there a plan to Http version 1.0 be supported? It's legacy but used with some bots and tools. `Unsupported HTTP version 1.0`
Question up front: is it possible to use this crate with tokio? I'm interested in building a library for using the Spotify API; the existing [rspotify](https://github.com/ramsayleung/rspotify) seems to be tied...