Async::HTTP An asynchronous client and server implementation of HTTP/1.0, HTTP/1.1 and HTTP/2 including TLS. Support for streaming requests…
Async::HTTP An asynchronous client and server implementation of HTTP/1.0, HTTP/1.1 and HTTP/2 including TLS. Support for streaming requests…
An asynchronous client and server implementation of HTTP/1.0, HTTP/1.1 and HTTP/2 including TLS. Support for streaming requests and responses. Built on top of async, io-endpoint and io-stream. falcon provides a rack-compatible server.
Please see the project documentation for more details.
Getting Started - This guide explains how to make HTTP requests and serve HTTP responses with Async::HTTP.
Choosing a Client - This guide explains how to choose between ruby:Async::HTTP::Internet, ruby:Async::HTTP::Client, and higher-level interfaces for libraries.
Concurrent Requests and Connection Pooling - This guide explains how to run HTTP requests concurrently while keeping request fan-out, connection usage, and resource life cycles bounded.
Testing - This guide explains how to test Async::HTTP clients and servers without depending on external HTTP services.
Please see the project releases for all releases.
400 Bad Request for any Protocol::HTTP::BadRequest raised while parsing HTTP/1 or HTTP/2 requests, include the exception class name without reflecting request data, and avoid reporting them as unhandled server errors.RST_STREAM(NO_ERROR) as an orderly HTTP/2 stream closure while still failing requests whose streams close before any response headers are received.GOAWAY are removed from availability immediately, but remain in the pool until the server has finished answering the streams it accepted. The connection is closed after its final user releases it, so those requests no longer fail with EOFError: Connection closed with N active stream(s)!.Async::HTTP::Protocol::HTTP1::Server#each without reporting them as server failures.Async::HTTP::Endpoint.INTERNAL_ERROR before returning a response.metrics and traces optional runtime dependencies. Applications that use the providers should depend on the corresponding gem and require the provider explicitly.async-http.async-http.async-http.We welcome contributions to this project.
git checkout -b my-new-feature).git commit -am 'Add some feature.').git push origin my-new-feature).To run the test suite:
$ bundle exec susTo make a new release:
$ bundle exec bake gem:release:patch # or minor or majorIn order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.
This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.
No open issues yet, or sync has not completed.