HTTP Client Top

I just announced the new Learn Spring course, focused on the fundamentals of Spring 5 and Spring Boot 2:


1. Introduction

In this tutorial, we’ll explore Java 9’s new incubating HttpClient.

Until very recently, Java provided only the HttpURLConnection API – which is low-level and isn’t known for being feature-rich and user-friendly.

Therefore, some widely used third-party libraries were commonly used – such as Apache HttpClient, Jetty, and Spring’s RestTemplate.

2. Initial Setup

The HTTP Client module is bundled as an incubator module in JDK 9 and supports HTTP/2 with backward compatibility still facilitating HTTP/1.1.

To use it, we need to define our module using a file which also indicates the required module to run our application:

module com.baeldung.java9.httpclient {   
  requires jdk.incubator.httpclient;

3. HTTP Client API Overview

Unlike HttpURLConnection, HTTP Client provides synchronous and asynchronous request mechanisms.

The API consists of 3 core classes:

  • HttpRequestrepresents the request to be sent via the HttpClient
  • HttpClientbehaves as a container for configuration information common to multiple requests
  • HttpResponserepresents the result of an HttpRequest call

We’ll examine each of them in more details in the following sections. First, let’s focus on a request.

4. HttpRequest

HttpRequest, as the name suggests, is an object which represents request we want to send. New instances can be created using HttpRequest.Builder.

We can get it by calling HttpRequest.newBuilder(). Builder class provides a bunch of methods which we can use to configure our request.

We’ll cover the most important ones.

4.1. Setting URI

The first thing we have to do when creating a request is to provide the URL.

We can do that in two ways – by using the constructor for Builder with URI parameter or by calling method uri(URI) on the Builder instance:

HttpRequest.newBuilder(new URI(""))
  .uri(new URI(""))

The last thing we have to configure to create a basic request is an HTTP method.

4.2. Specifying the HTTP Method

We can define the HTTP method which our request will use by calling one of the methods from Builder:

  • GET()
  • POST(BodyProcessor body)
  • PUT(BodyProcessor body)
  • DELETE(BodyProcessor body)

We’ll cover BodyProcessor in detail, later. Now, let’s just create a very simple GET request example:

HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))

This request has all parameters required by HttpClient. However, sometimes we need to add additional parameters to our request; here are some important ones are:

  • the version of the HTTP protocol
  • headers
  • a timeout

4.3. Setting HTTP Protocol Version

The API fully leverages the HTTP/2 protocol and uses it by default but we can define which version of the protocol we want to use.

HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))

Important to mention here is that the client will fallback to, e.g., HTTP/1.1 if HTTP/2 isn’t supported.

4.4. Setting Headers

In case we want to add additional headers to our request, we can use the provided builder methods.

We can do that in one of two ways:

  • passing all headers as key-value pairs to the headers() method or by
  • using header() method for the single key-value header:
HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))
  .headers("key1", "value1", "key2", "value2")

HttpRequest request2 = HttpRequest.newBuilder()
  .uri(new URI(""))
  .header("key1", "value1")
  .header("key2", "value2")

The last useful method we can use to customize our request is a timeout().

4.5. Setting a Timeout

Let’s now define the amount of time we want to wait for a response.

If the set time expires, a HttpTimeoutException will be thrown; the default timeout is set to infinity.

The timeout can be set with the Duration object – by calling method timeout() on the builder instance:

HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))
  .timeout(Duration.of(10, SECONDS))

5. Setting a Request Body

We can add a body to a request by using the request builder methods: POST(BodyProcessor body), PUT(BodyProcessor body) and DELETE(BodyProcessor body).

The new API provides a number of BodyProcessor implementations out-of-the-box which simplify passing the request body:

  • StringProcessor (reads body from a String, created with HttpRequest.BodyProcessor.fromString)
  • InputStreamProcessor (reads body from an InputStream, created with HttpRequest.BodyProcessor.fromInputStream)
  • ByteArrayProcessor (reads body from a byte array, created with HttpRequest.BodyProcessor.fromByteArray)
  • FileProcessor (reads body from a file at the given path, created with HttpRequest.BodyProcessor.fromFile)

In case we don’t need a body, we can simply pass in an HttpRequest.noBody():

HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))

5.1. StringBodyProcessor

Setting a request body with any BodyProcessor implementation is very simple and intuitive.

For example, if we want to pass a simple String as a body, we can use StringBodyProcessor.

As we already mentioned, this object can be created with a factory method fromString(); it takes just a String object as an argument and creates a body from it:

HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))
  .headers("Content-Type", "text/plain;charset=UTF-8")
  .POST(HttpRequest.BodyProcessor.fromString("Sample request body"))

5.2. InputStreamBodyProcessor

To do that, the InputStream has to be passed as a Supplier (to make its creation lazy), so it’s a little bit different than described above StringBodyProcessor.

However, this is also quite straightforward:

byte[] sampleData = "Sample request body".getBytes();
HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))
  .headers("Content-Type", "text/plain;charset=UTF-8")
   .fromInputStream(() -> new ByteArrayInputStream(sampleData)))

Notice how we used a simple ByteArrayInputStream here; that can, of course, be any InputStream implementation.

5.3. ByteArrayProcessor

We can also use ByteArrayProcessor and pass an array of bytes as the parameter:

byte[] sampleData = "Sample request body".getBytes();
HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))
  .headers("Content-Type", "text/plain;charset=UTF-8")

5.4. FileProcessor

To work with a File, we can make use of the provided FileProcessor; its factory method takes a path to the file as a parameter and creates a body from the content:

HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))
  .headers("Content-Type", "text/plain;charset=UTF-8")

We covered how to create HttpRequest and how to set additional parameters in it.

Now it’s time to take a deeper look at HttpClient class which is responsible for sending requests and receiving responses.

6. HttpClient

All requests are sent using HttpClient which can be instantiated using the HttpClient.newBuilder() method or by calling HttpClient.newHttpClient().

It provides a lot of useful and self-describing methods we can use to handle our request/response.

Let’s cover some of these here.

6.1. Setting a Proxy

We can define a proxy for the connection. Just merely call proxy() method on a Builder instance:

HttpResponse<String> response = HttpClient
  .send(request, HttpResponse.BodyHandler.asString());

In our example, we used the default system proxy.

6.2. Setting the Redirect Policy

Sometimes the page we want to access has moved to a different address.

In that case, we’ll receive HTTP status code 3xx, usually with the information about new URI. HttpClient can redirect the request to the new URI automatically if we set the appropriate redirect policy.

We can do it with the followRedirects() method on Builder:

HttpResponse<String> response = HttpClient.newBuilder()
  .send(request, HttpResponse.BodyHandler.asString());

All policies are defined and described in enum HttpClient.Redirect.

6.3. Setting Authenticator for a Connection

An Authenticator is an object which negotiates credentials (HTTP authentication) for a connection.

It provides different authentication schemes (like e.g., basic or digest authentication). In most cases, authentication requires username and password to connect to a server.

We can use PasswordAuthentication class which is just a holder of these values:

HttpResponse<String> response = HttpClient.newBuilder()
  .authenticator(new Authenticator() {
    protected PasswordAuthentication getPasswordAuthentication() {
      return new PasswordAuthentication(
  .send(request, HttpResponse.BodyHandler.asString());

In the example above we passed the username and password values as a plaintext; of course, in a production scenario, this will have to be different.

Note that not every request should use the same username and password. The Authenticator class provides a number of getXXX (e.g., getRequestingSite()) methods that can be used to find out what values should be provided.

Now we’re going to explore one of the most useful features of new HttpClient – asynchronous calls to the server.

6.4. Send Requests – Sync vs. Async

New HttpClient provides two possibilities for sending a request to a server:

  • send(…) – synchronously (blocks until the response comes)
  • sendAsync(…) – asynchronously (doesn’t wait for the response, non-blocking)

Up until now, the send(...) method naturally waits for a response:

HttpResponse<String> response = HttpClient.newBuilder()
  .send(request, HttpResponse.BodyHandler.asString());

This call returns an HttpResponse object, and we’re sure that the next instruction from our application flow will be executed only when the response is already here.

However, it has a lot of drawbacks especially when we are processing large amounts of data.

So, now, we can use sendAsync(...) method – which returns CompletableFeature<HttpResponse>to process a request asynchronously:

CompletableFuture<HttpResponse<String>> response = HttpClient.newBuilder()
  .sendAsync(request, HttpResponse.BodyHandler.asString());

The new API can also deal with multiple responses, and stream the request and response bodies:

List<URI> targets = Arrays.asList(
  new URI(""),
  new URI(""));
HttpClient client = HttpClient.newHttpClient();
List<CompletableFuture<String>> futures =
  .map(target -> client
    .thenApply(response -> response.body()))

6.5. Setting Executor for Asynchronous Calls

We can also define an Executor which provides threads to be used by asynchronous calls.

This way we can, for example, limit the number of threads used for processing requests:

ExecutorService executorService = Executors.newFixedThreadPool(2);

CompletableFuture<HttpResponse<String>> response1 = HttpClient.newBuilder()
  .sendAsync(request, HttpResponse.BodyHandler.asString());

CompletableFuture<HttpResponse<String>> response2 = HttpClient.newBuilder()
  .sendAsync(request, HttpResponse.BodyHandler.asString());

By default, the HttpClient uses executor java.util.concurrent.Executors.newCachedThreadPool().

6.6. Defining a CookieManager

With new API and builder, it’s straightforward to set a CookieManager for our connection. We can use builder method cookieManager(CookieManager cookieManager) to define client-specific CookieManager.

Let’s, for example, define CookieManager which doesn’t allow to accept cookies at all:

  .cookieManager(new CookieManager(null, CookiePolicy.ACCEPT_NONE))

In case our CookieManager allows cookies to be stored, we can access them by checking CookieManager from our HttpClient:


Now let’s focus on the last class from Http API – the HttpResponse.

7. HttpResponse Object

The HttpResponse class represents the response from the server. It provides a number of useful methods – but two the most important are:

  • statusCode() – returns status code (type int) for a response (HttpURLConnection class contains possible values)
  • body() – returns a body for a response (return type depends on the response BodyHandler parameter passed to the send() method)

The response object has other useful method which we’ll cover like uri(), headers(), trailers() and version().

7.1. URI of Response Object

The method uri() on the response object returns the URI from which we received the response.

Sometimes it can be different than URI in the request object, because a redirection may occur:

  .toString(), equalTo(""));
  .toString(), equalTo(""));

7.2. Headers from Response

We can obtain headers from the response by calling method headers() on a response object:

HttpResponse<String> response = HttpClient.newHttpClient()
  .send(request, HttpResponse.BodyHandler.asString());
HttpHeaders responseHeaders = response.headers();

It returns HttpHeaders object as a return type. This is a new type defined in jdk.incubator.http package which represents a read-only view of HTTP Headers.

It has some useful methods which simplify searching for headers value.

7.3. Get Trailers from Response

The HTTP response may contain additional headers which are included after the response content. These headers are called trailer headers.

We can obtain them by calling method trailers() on HttpResponse:

HttpResponse<String> response = HttpClient.newHttpClient()
  .send(request, HttpResponse.BodyHandler.asString());
CompletableFuture<HttpHeaders> trailers = response.trailers();

Note that trailers() method returns CompletableFuture object.

7.4. Version of the Response

The method version() defines which version of HTTP protocol was used to talk with a server.

Remember, that even if we define that we want to use HTTP/2, the server can answer via HTTP/1.1.

The version in which the server answered is specified in the response:

HttpRequest request = HttpRequest.newBuilder()
  .uri(new URI(""))
HttpResponse<String> response = HttpClient.newHttpClient()
  .send(request, HttpResponse.BodyHandler.asString());
assertThat(response.version(), equalTo(HttpClient.Version.HTTP_1_1));

8. Java 11 Http Client

The major change in Java 11 was standardization of HTTP client API that implements HTTP/2 and Web Socket. It aims to replace the legacy HttpUrlConnection class which has been present in the JDK since the very early years of Java.

The change was implemented as a part of JEP 321.

8.1. Major changes as part of  JEP 321

  1. The incubated HTTP API from Java 9 is now officially incorporated into the Java SE API. The new HTTP APIs can be found in*
  2. The newer version of the HTTP protocol is designed to improve the overall performance of sending requests by a client and receiving responses from the server. This is achieved by introducing a number of changes such as stream multiplexing, header compression and push promises.
  3. As of Java 11, the API is now fully asynchronous (the previous HTTP/1.1 implementation was blocking). Asynchronous calls are implemented using  CompletableFuture.The CompletableFuture implementation takes care of applying each stage once the previous one has finished, so this whole flow is asynchronous.
  4. The new HTTP client API provides a standard way to perform HTTP network operations with support for modern Web features such as HTTP/2, without the need to add third-party dependencies.
  5. The new APIs provide native support for HTTP 1.1/2 WebSocket. The core classes and interface providing the core functionality include:
  • The HttpClient class,
  • The HttpRequest class,
  • The HttpResponse<T> interface,
  • The WebSocket interface,

8.2. Problems with the Pre Java 11 HTTP Client

The existing HttpURLConnection API and its implementation had numerous problems:

  • URLConnectionAPI was designed with multiple protocols which are now no longer functioning (FTP, gopher, etc.).
  • The API predates HTTP/1.1 and is too abstract.
  • It works in blocking mode only (i.e., one thread per request/response).
  • It is very hard to maintain.

9. Changes in Http Client with Java 11

9.1. Introduction of Static Factory Classes

New static factory classes BodyPublishers, BodySubscribers and BodyHandlers are introduced that includes existing implementations of BodyPublisher, BodySubscriber and BodyHandler.

These are used to perform useful common tasks, such as handling the response body as a String or streaming the body to a File.

For e.g. in Pre Java 11 we had to do something like this:

HttpResponse<String> response = client.send(request, HttpResponse.BodyHandler.asString());

Which we can now simplify as:

HttpResponse<String> response = client.send(request, BodyHandlers.ofString());

Also, the name of static methods has been standardized for more clarity.

For e.g. methods names like fromXxx are used when we are using them as adapters or names like ofXxx when we are creating pre-defined handlers/subscribers.

9.2. Fluent Methods for common body types

Convenient factory methods for created publishers and handlers for handling common body types have been introduced.

For e.g. we have below fluent methods for creating publishers from bytes, files and strings:


Similarly, for creating handlers from these common body types we can use:


9.3. Other API Changes

1. With this new API,  we will be using BodyHandlers.discarding() and BodyHandlers.replacing(value) instead of discard(Object replacement):

HttpResponse<?> response1 = HttpClient.newHttpClient()
            .send(request, BodyHandlers.discarding());
HttpResponse<?> response1 = HttpClient.newHttpClient()
            .send(request, BodyHandlers.replacing(value));

2. New method ofLines() in BodyHandlers is added to handle streaming of the response body as a Stream of lines.

3. fromLineSubscriber method is added in BodyHandlers class that can be used as an adapter between a BodySubscriber and a text-based Flow.Subscriber that parses text line by line.

4. Added a new BodySubscriber.mapping in BodySubscribers class that can be used for mapping from one response body type to another by applying the given function to the body object.

5. In HttpClient.Redirect, enum constants SAME_PROTOCOL and SECURE policy are replaced with a new enum NORMAL.

10. Handling push promises in HTTP/2

New Http client supports push promises through PushPromiseHandler interface

It allows the server to “push” content to the client additional resources while requesting the primary resource, saving more roundtrip and as a result, improves performance in page rendering.

It is really the multiplexing feature of HTTP/2 that allows us to forget about resource bundling. For each resource, the server sends a special request, known as a push promise to the client.

Push promises received, if any, are handled by the given PushPromiseHandler. A null valued PushPromiseHnadler rejects any push promises.

The HttpClient has an overloaded sendAsync method that allows us to handle such promises, as shown in the below example.

Let’s first create a PushPromiseHandler:

private static PushPromiseHandler<String> pushPromiseHandler() {
    return (HttpRequest initiatingRequest, 
        HttpRequest pushPromiseRequest, 
        CompletableFuture<HttpResponse<String>>> acceptor) -> {
            .thenAccept(resp -> {
                System.out.println(" Pushed response: " + resp.uri() + ", headers: " + resp.headers());
        System.out.println("Promise request: " + pushPromiseRequest.uri());
        System.out.println("Promise request: " + pushPromiseRequest.headers());

Next, let’s use sendAsync method to handle this push promise:

httpClient.sendAsync(pageRequest, BodyHandlers.ofString(), pushPromiseHandler())
    .thenAccept(pageResponse -> {
        System.out.println("Page response status code: " + pageResponse.statusCode());
        System.out.println("Page response headers: " + pageResponse.headers());
        String responseBody = pageResponse.body();

11. Conclusion

In this article, we explored Java 9’s HttpClient API which provides a lot of flexibility and powerful features. The complete code used for Java 9’s HttpClient API is available over on GitHub.

We also explored the new changed in Java 11 HttpClient, that standardized the incubating HttpClient introduced in Java 9 with more powerful changes. The code snippets used for Java 11 Http Client is also available over Github.

Note: In the examples, we’ve used sample REST endpoints provided by

HTTP Client bottom

I just announced the new Learn Spring course, focused on the fundamentals of Spring 5 and Spring Boot 2:


newest oldest most voted
Notify of
Gagandeep kalra
Gagandeep kalra

is this NIO based Async or simple thread blocking one?

Grzegorz Piwowarek


Peter Verhas
Peter Verhas

How do you assign the request to a specific connection? HTTP/2.0 can multiplex several requests and responses into one connection. How do you open more than one connection to a server and then send several requests using one or the other connection?

How do you handle the HTTP push responses that you did not send a request? Is there any way to see what pushes were coming?

Loredana Crusoveanu

Hey Peter,

Thanks for the comment. I don’t see a way to control to assign a request to a connection from the HttpClient API. For push responses, have a look at the JDK 11 addition: