Open Source Java HTTP Clients

Jellyfin Android TV is a Jellyfin client for Android TV, Nvidia Shield, and Amazon Fire TV devices. We welcome all contributions and pull requests! If you have a larger feature in mind please open an issue so we can discuss the implementation before you start. Jellyfin is the volunteer-built media solution that puts you in control of your media. Stream to any device from your own server, with no strings attached. Your media, your server, your way. Jellyfin enables you to collect, manage, and stream your media. Run the Jellyfin server on your system and gain access to the leading free-software entertainment system, bells and whistles included.

Feign is a Java to HTTP client binder that was built primarily to make writing Java http clients easier. Inspired by previous projects Retrofit, JAXRS-2.0 and WebSocket, Feign was designed to reduce the complexity that is often involved in binding the Denominator uniformly to HTTP APIs, no matter the ReSTfulness. Feign works by processing annotations into a templatized request, to which arguments are applied in a straightforward manner before output. While it may only support text-based APIs, it simplifies system aspects dramatically and makes it much easier to unit test your conversions. Feign makes use of great tools like Jersey and CXF for writing Java clients for ReST or SOAP services. It also lets you write your own code on top of http libraries, and connects your code to http APIs with little overhead.

Fast Android Networking Library is a powerful library for doing any type of networking in Android applications which is made on top of OkHttp Networking Layer. Fast Android Networking Library takes care of each and everything. So you don't have to do anything, just make a request and listen for the response. The recent removal of HttpClient in Android Marshmallow(Android M) made other networking libraries obsolete. No other single library does and everything like making requests, downloading any type of file, uploading file, loading images from the network in ImageView, etc. There are some libraries but they are outdated. No other library provides a simple interface for doing all types of things in networking like setting priority, canceling, etc. As it uses Okio , No more GC overhead in android applications. Okio is made to handle GC overhead while allocating memory. Okio does some clever things to save CPU and memory.

Milkman is heavily inspired by Postman. But I got sick of all those electron-based applications that need ages and loads of memory to start up. Therefore, this is a JavaFx-based workbench for crafting requests/responses. It is not limited to e.g. HTTP (or more specifically rest) requests. Due to nearly everything being a plugin, other things are possible, like database requests or GRPC, GraphQl, etc. Request-types (e.g. Http Request), request-aspects (e.g. Headers, Body, etc), editors for request aspects (e.g. table-based editors for headers), importers, whatever it is, you can extend it. The core application only handles Workspaces with Environments, Collections, Requests, and their aspects. Several plugins are provided already that extend the core application to be a replacement for postman. Crafting and Executing Http/Rest requests with json highlighting. Support Proxy-server configuration and SSE.

Java Docker API Client. To start using docker-java , you need to add at least two dependencies. You will need an instance of DockerClientConfig to tell the library how to access Docker, which credentials to use to pull from Docker registries, etc. The builder is available and allows you to configure every property of the client. Should you need to customize the Jackson's ObjectMapper used by docker-java, you can create your own DockerClientConfig. Once you decided which transport to use, you will need to instantiate an HTTP client. Once you have an HTTP client, you can make raw requests to the Docker daemon directly. To get an instance of DockerClient, you need to pass both DockerClientConfig and DockerHttpClient.

JETTY HAS MOVED TO ECLIPSE!!!! The latest releases of Jetty are hosted from http://eclipse.org/jetty. Jetty is an open-source project providing a HTTP server, HTTP client and javax.servlet container.

NetTool is a developer tool for monitoring and manipulating application-level network messages, particularly useful for debugging web applications and web services. There are two components to NetTool: the HTTP Client, and the TCP Tunnel.

A SPARQL client for Amazon Neptune that includes AWS Signature Version 4 signing. Implemented as an RDF4J repository. SPARQL client for Amazon Neptune that includes AWS Signature Version 4 signing. Implemented as an RDF4J repository and Jena HTTP Client.

An asynchronous, callback-based Http client for Android built on top of Apache's HttpClient libraries. Make asynchronous HTTP requests, handle responses in anonymous callbacks. Requests use a thread pool to cap concurrent resource usage. Multipart file uploads with no additional third-party libraries. Tiny size overhead to your application, only 60kb for everything. Automatic smart request retries optimized for spotty mobile connections. Automatic gzip response decoding support for super-fast requests. Optional built-in response parsing into JSON (JsonHttpResponseHandler). Optional persistent cookie store, saves cookies into your app's SharedPreferences.

A Java library that provides accelerated downloads of HTTP/HTTPS URIs via the GET and POST methods. Works similar to download managers as requests are made in parallel and chunked for speed.

Fast, lightweight Web framework based on Netty; without too much dependency, and the core jar package is only 30KB. Configuration files can also be read in multiple environments, just add VM parameters, also ensure that the parameter name and file name are consistent.

A XML pull-parse library for Java 1.2, designed for processing XML protocol messages in the most efficient way possible. Contains a complete HTTP client library.

Flea2Flea is a pocket web server written in Java which enables ad-hoc peer-to-peer file sharing with anyone who has an http client (web browser). Files are only accessible while you are running Flea2Flea. You have absolute control.

HTTP Client Plugin is an Eclipse 3.3+ plugin that enables users to construct and execute HTTP protocol messages. It is intended to support protocol level testing of web components.

http-kit is a minimalist, event-driven, high-performance Clojure HTTP server/client library with WebSocket and asynchronous support. A simple, high-performance event-driven HTTP client+server for Clojure. HTTP Kit is an (almost) drop-in replacement for the standard Ring Jetty adapter. So you can use it with all your current libraries (e.g. Compojure) and middleware. Using an event-driven architecture like Nginx, HTTP-kit is very, very fast. It comfortably handles tens of thousands of requests/sec on even midrange hardware. Here is another test about how it stacks up with others. It's not only fast, but efficient! Each connection costs nothing but a few kB of memory. RAM usage grows O(n) with connections. Written from the ground-up to be lean, the entire client/server is available as a single ~90kB JAR with zero dependencies and ~3k lines of (mostly Java) code. Synchronous is simple. Asynchronous is fast & flexible.

HTTPSession will provide a complete java library to manage HTTP client sessions. The features (will) include: cookie management, HTTP authentication, referer management, navigation history, refresh statements and HTTP redirections handling.

HyperCES is a Cookie Encapsulation System (CES). The purpose of a CES is to act as an intermediary between an HTTP client and a web server, to handle cookies on the client's behalf. HyperCES does this by adding a session identifier to the URL.

Jandy is an internet development framework based on Indy, designed to make writing web clients and servers easier. Currently only the HTTP client and HTTP server frameworks are working, but other protocols will be included, like FTP, POP3, SMTP, etc.

This library defines an object oriented representation of the GitHub API. By "object oriented" we mean there are classes that correspond to the domain model of GitHub (such as GHUser and GHRepository), operations that act on them as defined as methods (such as GHUser.follow()), and those object references are used in favor of using string handle (such as GHUser.isMemberOf(GHOrganization) instead of GHUser.isMemberOf(String)) The library supports both github.com and GitHub Enterprise. Most of the GitHub APIs are covered, although there are some corners that are still not yet implemented. The library allows connecting to GitHub via several different authentication mechanisms. This library defines a common convention so that applications using this library will look at a consistent location. In this convention, the library looks at ~/.github property file. The content of the files depends on the way you want this library to authenticate as shown.

Forwards non-NTLM HTTP client requests to an NTLM proxy server (ie. Microsoft IAS). Can also forward a local port to a remote machine.

Jinku is an opensource web dumper written in Java. Currently it supports only HTTP/1.0. Related keywords include HTTP Client, HTTP Browser, Web Client and Web Browser.

Nginx module for embedding Clojure or Java or Groovy programs, typically those Ring based handlers. Compatible with Ring and obviously supports those Ring-based frameworks, such as Compojure, etc. HTTP Services by using Clojure / Java / Groovy to write simple handlers for HTTP services. A build-in Jersey container to support java standard RESTful web services (JAX-RS 2.0). Tomcat 8 embedding support (so servlet 3.1/jsp/sendfile/JSR-356 WebSocket work within nginx!). Dynamic proxying by using Clojure / Java / Groovy to write a simple nginx rewrite handler to set var or return errors before a proxy pass or content ring handler. The non-blocking coroutine-based socket is Compatible with Java Socket API and works well with largely existing java libraries such as apache HTTP client, mysql jdbc drivers. With this feature, one java main thread can handle thousands of connections. Handle multiple sockets parallel in sub coroutines.

This library is based on the Http protocol and encapsulates the OkHttp network request framework. It is easier to use than Retrofit, supports RxJava, RxJava2, supports custom caching, and supports batch breakpoint download management and batch upload management functions. Completely imitating WeChat's image selection library, it comes with rectangular image cropping and circular image cropping functions, which can be downloaded and used if necessary. Similar to Qzone, WeChat Moments, Weibo homepage, etc., the Jiugongge control that displays pictures automatically determines the size of the picture and the size of the control according to the number of pictures, uses the Adapter mode to set the picture, provides external interface callbacks, and uses the interface to load pictures, supporting arbitrary Image loading frameworks such as: Glide, ImageLoader, xUtils3, Picasso, etc., support click on the image to preview the large image in full screen.

Proxyee is a JAVA-written HTTP proxy server library that supports HTTP, HTTPS, and WebSocket protocols, and supports MITM (Man-in-the-middle), which can capture and tamper with HTTP, and HTTPS packets. The CA certificate (src/resources/ca.crt) from the project needs to be imported to a trusted root certificate authority. The CA certificate (src/resources/ca.crt) from the project needs to be imported to a trusted root certificate authority. You can use the CertDownIntercept interceptor to enable the web certificate download feature.

Reactor Netty offers non-blocking and backpressure-ready TCP/HTTP/UDP/QUIC clients & servers based on Netty framework. With Gradle from repo.spring.io or Maven Central repositories (stable releases only). Reactor is a fourth-generation reactive library, based on the Reactive Streams specification, for building non-blocking applications on the JVM. Reactor is fully non-blocking and provides efficient demand management. It directly interacts with Java's functional API, CompletableFuture, Stream, and Duration. Reactor offers two reactive and composable APIs, Flux [N] and Mono [0|1], which extensively implement Reactive Extensions. Well-suited for a microservices architecture, Reactor offers backpressure-ready network engines for HTTP (including Websockets), TCP, and UDP.