Is there any handling of connection pooling on java.net.HttpClient?

Question

I want to use Java 11 HttpClient and send multiple requests on the same address with the use of the Keep-Alive parameter of HTTP 1.1. I know that there is similar functionality for Apache HTTP Client, but is there anything like that for Java API's client?

Answer 1

Yes - HTTP/1.1 connections are kept alive by default, unless the maximum size of the pool is exceeded, in which case the oldest idle connection in the pool (the connection which is closest to its expiration date) is closed to make room for the new connection. However multiple connections to the same host will be opened if the requests are made concurrently.