Apache HttpClient user agent
Apache HttpClient, part of the Apache HttpComponents project, is a widely used Java HTTP client. Its default user agent contains an Apache-HttpClient token with a version. It is one of several common Java HTTP clients (alongside OkHttp and the JDK's own client) and marks server-side automation, not a browser.
What this means
Apache HttpClient is a mature Java HTTP client from the Apache HttpComponents project, used in countless backend services and tools. Its default user agent includes an Apache-HttpClient product token with a version.
It is a server-side client with no rendering engine. A request carrying the Apache-HttpClient token is a Java program making HTTP calls, whether a legitimate integration, a crawler, or a scraper.
Distinguishing Java clients
The Java ecosystem has several common HTTP clients: Apache HttpClient (Apache-HttpClient token), OkHttp (an okhttp token), and the JDK's built-in HttpClient (which may send a Java-style token or none, depending on configuration). Matching the specific token tells you which library, which can help attribute traffic to a particular tool or SDK.
As always, developers frequently override the default with a custom user agent, so absence of the Apache-HttpClient token does not rule out Apache HttpClient.
- Default token: Apache-HttpClient plus version
- Sibling clients: OkHttp, JDK HttpClient (different signatures)
- Often replaced by a custom application user agent
Allow, rate-limit, or block
For first-party Java integrations, set a descriptive custom user agent and authenticate, so the traffic is clearly yours. For unwanted automation showing the raw token, rate-limit by token plus behaviour rather than blocking the exact string, which is easily changed.
The user agent is one signal; never treat it as access control on its own.
How it appears in analytics and logs
A user agent containing an Apache-HttpClient token is a Java program using Apache HttpComponents to make requests — automation, not a human visit. As with all libraries, the default is often replaced by a custom application user agent.
Diagnostic use case
Identify server-side Java traffic that uses Apache HttpClient, and distinguish it from OkHttp and other Java clients when triaging integrations and scrapers.
What WebmasterID can help detect
WebmasterID classifies Apache HttpClient traffic as scripted automation and distinguishes it from other Java clients, so server-side integrations and scrapers appear in bot-intelligence rather than human metrics.
Common mistakes
- Confusing Apache HttpClient with OkHttp — they use different tokens.
- Counting Apache HttpClient requests as human visits.
- Assuming the token is always present, when many apps customise it.
Privacy and accuracy notes
Apache HttpClient is identified from the user-agent token alone — a program, not a person. WebmasterID records it as automation, separate from human analytics.
Related pages
- Java and OkHttp user agents
JVM HTTP clients send recognisable default user agents: Java's built-in URL connection uses a Java/version token, and the widely used OkHttp library uses an okhttp/version token. Both mark scripted or app traffic from the Java ecosystem, including many Android apps. This page covers the two patterns.
- Go-http-client user agent
Programs built with Go's standard net/http client send a default user agent of the form Go-http-client/x.y. Seeing it means a Go application made the request — common for backend services, CLIs, and integrations. It is honest automation, not a browser, and the default can be overridden. This page covers the pattern.
- API client user agents (Postman, etc.)
Developers exercise APIs with tools like Postman, Insomnia, and HTTPie, each of which sends a recognisable default user agent (for example a PostmanRuntime token). Seeing these means someone is testing or scripting against your API, not browsing your pages. This page covers the patterns and how to read them.
- Bot intelligence
Attribute Java HTTP-client traffic to the right library, not to humans.
Sources and verification notes
- Apache HttpComponents — HttpClientDefault user agent contains an Apache-HttpClient token.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.