Async::HTTP
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 and async-io. falcon provides a rack-compatible server.
Usage
Please browse the source code index or refer to the guides below.
Getting Started
This guide explains how to get started with Async::HTTP.
Testing
This guide explains how to use Async::HTTP clients and servers in your tests.
Releases
Please browse the releases for more details.
v0.87.0
v0.86.0
- Add support for HTTP/2
NO_RFC7540_PRIORITIES. See https://www.rfc-editor.org/rfc/rfc9218.html for more details.
v0.84.0
- Minor consistency fixes to
Async::HTTP::Internetsingleton methods.
v0.82.0
protocol-http1introduces a line length limit for request line, response line, header lines and chunk length lines.
v0.81.0
- Expose
protocolandendpointas tags toasync-poolfor improved instrumentation.
v0.77.0
- Improved HTTP/1 connection handling.
- The input stream is no longer closed when the output stream is closed.
v0.76.0
Async::HTTP::Body::Writableis moved toProtocol::HTTP::Body::Writable.- Remove
Async::HTTP::Body::Delayedwith no replacement. - Remove
Async::HTTP::Body::Slowloriswith no replacement.
v0.75.0
- Better handling of HTTP/1 <-> HTTP/2 proxying, specifically upgrade/CONNECT requests.
v0.74.0
v0.73.0
See Also
- benchmark-http — A benchmarking tool to report on web server concurrency.
- falcon — A rack compatible server built on top of
async-http. - async-websocket — Asynchronous client and server websockets.
- async-rest — A RESTful resource layer built on top of
async-http. - async-http-faraday — A faraday adapter to use
async-http.
Contributing
We welcome contributions to this project.
- Fork it.
- Create your feature branch (
git checkout -b my-new-feature). - Commit your changes (
git commit -am 'Add some feature'). - Push to the branch (
git push origin my-new-feature). - Create new Pull Request.
Developer Certificate of Origin
In 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.
Community Guidelines
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.