AsyncHttpClient/async-http-client is tracked by TopGit as a backend project, with 6.4k stars on GitHub, written primarily in Java. Asynchronous, non-blocking HTTP & WebSocket client for the JVM
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
AsyncHttpClient (AHC) is a high-performance, asynchronous HTTP client for Java
built on top of Netty.
It supports HTTP/1.1, HTTP/2, and WebSocket protocols.
Table of Contents
Features
Requirements
Installation
Quick Start
Configuration
HTTP Requests
Handling Responses
HTTP/2
WebSocket
Authentication
Proxy Support
Community
License
Features
HTTP/2 with multiplexing — enabled by default over TLS via ALPN,
with connection multiplexing and GOAWAY handling
HTTP/1.1 and HTTP/1.0 — connection pooling and keep-alive
WebSocket — text, binary, and ping/pong frame support
Asynchronous API — non-blocking I/O with ListenableFuture
and CompletableFuture
Compression — automatic gzip, deflate, Brotli, and Zstd decompression
Authentication — Basic, Digest, NTLM, SPNEGO/Kerberos, and SCRAM-SHA-256
Proxy — HTTP, SOCKS4, and SOCKS5 with CONNECT tunneling
Native transports — optional Epoll, KQueue, and io_uring
Request/response filters — intercept and transform at each stage
Cookie management — RFC 6265-compliant cookie store
Multipart uploads — file, byte array, input stream, and string parts
AHC decompresses Brotli, Zstd and Snappy response bodies on demand with Netty's pull-based Decompressor API, which
exists since Netty 4.2.17. If you override AHC's Netty version with an older one, these codings are still
decompressed, but as soon as they are read, so a suspended response does not hold them back. The same applies to Zstd
if the system property io.netty.compression.defaultMaxForwardBytes is set to zero or a negative value. gzip and
deflate are not affected.
Over HTTP/1.1, a compressed response body that ends in the middle of its compressed stream, for example because a
body delimited by the connection was cut off, fails the request with a DecompressionException; a body without any
bytes completes. Not every such end is noticed. A gzip or Zstd body cut exactly between two of its members or frames
looks complete, as the stream may end after any of them, and Snappy has no end marker, so a body cut between two of its
chunks looks complete too. With zstd-jni older than 1.5.7-26, a Zstd body of several frames also completes when it is
cut inside a frame that started in the same chunk as the end of the previous one. zstd-jni is an optional dependency, so
the version your application declares is the one used: use 1.5.7-26 or later. HTTP/2 response bodies are not checked,
and neither are transfer codings such as Transfer-Encoding: gzip, nor Brotli, Zstd and Snappy bodies decompressed as
soon as they are read, as described above.
Quick Start
Import the DSL helpers:
import static org.asynchttpclient.Dsl.*;
Create a client, execute a request, and read the response:
Note:AsyncHttpClient instances are long-lived, shared resources.
Always close them when done. Creating a new client per request will degrade
performance due to repeated thread pool and connection pool creation.
For fine-grained control, implement AsyncHandler directly. This lets you
inspect status, headers, and body chunks as they arrive and abort early:
Future<Integer> future = client
.prepareGet("https://www.example.com/")
.execute(new AsyncHandler<>() {
private int status;
@Override
public State onStatusReceived(HttpResponseStatus s) {
status = s.getStatusCode();
return State.CONTINUE;
}
@Override
public State onHeadersReceived(HttpHeaders headers) {
return State.CONTINUE;
}
@Override
public State onBodyPartReceived(HttpResponseBodyPart part) {
return State.ABORT; // stop early — we only needed the status
}
@Override
public Integer onCompleted() {
return status;
}
@Override
public void onThrowable(Throwable t) {
t.printStackTrace();
}
});
HTTP/2
HTTP/2 is enabled by default for HTTPS connections via ALPN negotiation.
The client uses HTTP/2 when the server supports it and falls back to HTTP/1.1
otherwise. No additional configuration is required.
Connection multiplexing — concurrent streams over a single TCP connection
GOAWAY handling — graceful connection draining on server shutdown
PING keepalive — configurable ping frames to keep connections alive
When a handler suspends a response with ResponseBodyControl, the HTTP/2
per-stream window remains the buffering bound for that response. While at least
one response on a connection is suspended, AHC continues returning
connection-level credit so it cannot stall sibling streams. Connections with no
active suspension retain the normal 65,535-byte shared connection-window bound.
Once the last suspension ends, normal connection accounting resumes, although
credit already returned and data already queued cannot be revoked. Aggregate
queued response data during suspension can scale with the number of concurrent
streams. Use http2InitialWindowSize and http2MaxConcurrentStreams together
when an application needs a tighter aggregate bound.
How active is development on AsyncHttpClient/async-http-client?
The most recent commit recorded on AsyncHttpClient/async-http-client was 3 months ago, based on the GitHub push timestamp. The repository has 1.6k forks — one of the better signals of community interest.
How many stars does AsyncHttpClient/async-http-client have?
AsyncHttpClient/async-http-client has 6.4k GitHub stars — refresh the page for the live number, or check github.com/AsyncHttpClient/async-http-client. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What else is in the Backend space?
AsyncHttpClient/async-http-client is tracked by TopGit under the Backend category, alongside 6 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What language is AsyncHttpClient/async-http-client written in?
AsyncHttpClient/async-http-client is written primarily in Java. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is AsyncHttpClient/async-http-client associated with?
GitHub's repository topics for AsyncHttpClient/async-http-client: "ahc", "async", "asynchttpclient", "http-client", "java", "netty". TopGit's editorial category is Backend.
Where do I read more about AsyncHttpClient/async-http-client?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/AsyncHttpClient/async-http-client is the definitive source.
Why is AsyncHttpClient/async-http-client categorized under Backend?
TopGit places AsyncHttpClient/async-http-client in the Backend category based on its GitHub topics and description (tagged: "ahc", "async", "asynchttpclient"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Still deciding about async-http-client?
One click hands the question to an AI along with this page — see what it says about async-http-client.