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.
Please see the project documentation for more details.
-
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.
Please see the project releases for all releases.
- Improved HTTP/1 connection handling.
- The input stream is no longer closed when the output stream is closed.
Async::HTTP::Body::Writable
is moved toProtocol::HTTP::Body::Writable
.- Remove
Async::HTTP::Body::Delayed
with no replacement. - Remove
Async::HTTP::Body::Slowloris
with no replacement.
- Better handling of HTTP/1 <-> HTTP/2 proxying, specifically upgrade/CONNECT requests.
- 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
.
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.
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.
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.