Unofficial, unaffiliated and unassociated fork of https://github.com/googleapis/google-http-java-client for internal use in Cryptomator for Android.
Important
This project is provided under the terms of the Apache License, Version 2.0; while it is made available to the public, it is important to note that this repository is not intended for public use and therefore no support is provided whatsoever.
For a project designed for use by the public, please refer to the original repository.
An excerpt from the README of the original project is reproduced below for your convenience and to provide proper attribution.
This project is not affiliated, associated, endorsed by, or in any way officially connected with Google, or any of its subsidiaries or its affiliates.
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
- The google-http-client-jackson2 and google-http-client-appengine modules require Java 8 or higher due to their dependencies.
- 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 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.