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 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.

Releases

Please see the project releases for all releases.

v0.82.0

• protocol-http1 introduces a line length limit for request line, response line, header lines and chunk length lines.

v0.81.0

• Expose protocol and endpoint as tags to async-pool for 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::Writable is moved to Protocol::HTTP::Body::Writable.
• Remove Async::HTTP::Body::Delayed with no replacement.
• Remove Async::HTTP::Body::Slowloris with no replacement.

v0.75.0

• Better handling of HTTP/1 <-> HTTP/2 proxying, specifically upgrade/CONNECT requests.

v0.74.0

• Async::HTTP::Internet accepts keyword arguments

v0.73.0

• Update support for interim_response

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.

1. Fork it.
2. Create your feature branch (git checkout -b my-new-feature).
3. Commit your changes (git commit -am 'Add some feature').
4. Push to the branch (git push origin my-new-feature).
5. 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.