async-h1 icon indicating copy to clipboard operation
async-h1 copied to clipboard

Asynchronous HTTP/1.1 in Rust

Results 38 async-h1 issues
Sort by recently updated
recently updated
newest added

I've found that `client` example fails with nginx on raspberrypi 4B. It's OK on local nginx and httpd on raspberry pi. I slightly modified `client` example to my environment. ```rust...

`async_h1::accept` panics with the following endpoint and request: ```rust |req| async move { let mut res = Response::new(StatusCode::Ok); res.set_body(req); Ok(res) } ``` ``` POST / HTTP/1.1 content-length: 0 ```

There are many [HTTP response headers](https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.6) that we should be sending back to the client. Here is a list of headers that we may want to support for every single...

We should have tests for: - [ ] server keepalive - [ ] server chunked encoding thanks!

Right now we hard code certain values for the server including max number of requests and keep alive timeout. We should have API that allows for this to be configured.

Finally got around to looking at this again and realized that I was looking at it from completely the wrong end last time. Fixes #199.

Also set MSRV to 1.63

This is a minor patch that removes `async-global-executor` as a dependency from this crate. Motivation: this avoids spawning the `cpu-count` threads that `async-global-executor` creates upon first use, in addition to...