The HttpClient will be receiving several updates in Java 26, let's review these changes and what Java users can expect.

Inside Java is a resource for Java developers, offering insights, tutorials, and updates on the Java programming language, platform, and ecosystem. With contributions from Java experts and members of the Java community, Inside Java covers a wide range of topics, including language features, performance optimizations, and upcoming releases. Developers can stay informed about the latest developments in the Java ecosystem, learn about new APIs and frameworks, and explore best practices for building robust and scalable Java applications.

Inside Java

Java 26 (releasing March 17th) brings several updates to the java.net.http.HttpClient. The headline addition is HTTP/3 support via JEP 517, with HTTP/2 remaining the default. Four strategies are outlined for handling HTTP/3 connectivity: optimistic HTTP/3-first, parallel HTTP/3 and HTTP/2 requests, pessimistic HTTP/2-first with ALT_SVC discovery, and HTTP/3-only mode. Other changes include a new BodyPublishers.ofFileChannel() method for uploading file regions, a fix for SSLParameters signature schemes being ignored during TLS handshake, an extended request timeout that now covers response body consumption, removal of Content-Length headers on non-POST/PUT requests without a body (per RFC9110), a NoSuchFileException to FileNotFoundException mapping fix, and a Max-Age cookie attribute precedence fix per RFC 6265.

HTTP Client Updates in Java 26 – Inside.java

Signature Schemes and Named Groups Usage Fix

Content-Length Removed for non-POST/PUT Requests