Apache-HttpClient is a bot in the HTTP clients and libraries category, operated by Apache Software Foundation.
Apache-HttpClient is the default user agent of the Apache HttpComponents library for Java. It shows up from back end integrations, Android apps and scrapers written in Java.
HTTP clients are programming libraries and command line tools. Developers use them for scripts, integrations and scrapers. Real browsers never send these user agents, so treat them as automated traffic and block them on pages meant for people.
Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.
Apache-HttpClient does not read robots.txt. The rules below record your policy, but they will not stop it. To actually block Apache-HttpClient, use a WAF rule as shown in the next section.
User-agent: Apache-HttpClient Disallow: /
User-agent: Apache-HttpClient Disallow: /private/ Disallow: /search
User-agent: Apache-HttpClient Allow: /blog/ Disallow: /
User-agent: Apache-HttpClient Allow: / User-agent: * Disallow: /
User-agent: Apache-HttpClient group, Apache-HttpClient ignores your User-agent: * rules, so repeat any that should still apply.Apache-HttpClient from Apache-HttpClient's user agent; check Apache Software Foundation's own documentation if it publishes a different robots.txt name.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Apache-HttpClient is a common tool for scrapers. Real readers never use it, so block it on article pages and keep it out of ad requests.
Transfon Security for publishersTraffic from Apache-HttpClient on landing pages is automated. It inflates clicks and visits, so filter it from campaign data and raise it with the ad network.
Transfon Security for advertisersPrice scrapers, stock checkers and card testing scripts often run on Apache-HttpClient. Block it on product, cart and checkout pages.
Transfon Security for e-commerceApache-HttpClient is normal for API clients but not for your web app. Allow it only on API routes that need a key, and rate limit it there.
Transfon Security for SaaS and APIsApache-HttpClient ignores robots.txt, so it has to be stopped when the request arrives. Transfon Security shows Apache-HttpClient by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.
Transfon Security
Apache-HttpClient is a bot in the HTTP clients and libraries category, operated by Apache Software Foundation. Apache-HttpClient is the default user agent of the Apache HttpComponents library for Java. It shows up from back end integrations, Android apps and scrapers written in Java.
No. Apache-HttpClient does not follow robots.txt, so a Disallow rule will not stop it. Block it by user agent at your server, CDN or WAF instead.
Block requests whose user agent contains "Apache-HttpClient/" at your server, CDN or WAF, because Apache-HttpClient does not read robots.txt. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so Apache-HttpClient may not follow it, and anyone can send Apache-HttpClient's user agent, so a fake Apache-HttpClient ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
HTTP clients are programming libraries and command line tools. Developers use them for scripts, integrations and scrapers. Real browsers never send these user agents, so treat them as automated traffic and block them on pages meant for people.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.