Google HTTP Client alternatives and similar libraries
Based on the "HTTP Clients" category.
Alternatively, view Google HTTP Client alternatives based on common mentions on social networks and blogs.
8.1 9.6 Google HTTP Client VS ArmeriaYour go-to microservice framework for any situation, from the creator of Netty et al. You can build any type of microservice leveraging your favorite technologies, including gRPC, Thrift, Kotlin, Retrofit, Reactive Streams, Spring Boot and Dropwizard.
7.6 8.2 L2 Google HTTP Client VS unirest-javaUnirest in Java: Simplified, lightweight HTTP client library.
3.7 7.7 Google HTTP Client VS Play WSStandalone Play WS, an async HTTP client with fluent API
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Google HTTP Client or a related project?
Google HTTP Client Library for Java
Written by Google, the Google HTTP Client Library for Java is a flexible, efficient, and powerful Java library for accessing any resource on the web via HTTP. The library has the following features:
- Pluggable HTTP transport abstraction that allows you to use any low-level library such as java.net.HttpURLConnection, Apache HTTP Client, or URL Fetch on Google App Engine.
- Efficient JSON and XML data models for parsing and serialization of HTTP response and request content. The JSON and XML libraries are also fully pluggable, and they include support for Jackson and Android's GSON libraries for JSON.
The library supports the following Java environments:
- Java 7 or higher
- Android 4.4 (Kit Kat)
- GoogleAppEngine Google App Engine
The following related projects are built on the Google HTTP Client Library for Java:
- Google OAuth Client Library for Java, for the OAuth 2.0 and OAuth 1.0a authorization standards.
- Google APIs Client Library for Java, for access to Google APIs.
This is an open-source library, and [contributions][contributions] are welcome.
Features marked with the
@Beta annotation at the class or method level are subject to change. They
might be modified in any way, or even removed, in any major release. You should not use beta
features if your code is a library itself (that is, if your code is used on the
CLASSPATH of users
outside your own control).
Deprecated non-beta features will be removed eighteen months after the release in which they are first deprecated. You must fix your usages before this time. If you don't, any type of breakage might result, and you are not guaranteed a compilation error.