JEP 517 proposes adding HTTP/3 support to Java's HTTP Client API (introduced in Java 11). The core API change is minimal: a new `HTTP_3` enum value for `HttpClient.Version`. The JEP also defines four strategies for negotiating which HTTP version to use when connecting to a server, since HTTP/3 uses UDP-based QUIC rather than TCP and cannot be upgraded from an existing TCP connection. HTTP/3 won't become the default (HTTP/2 remains preferred), and server-side HTTP/3, a QUIC API, and additional configuration options are out of scope for now. The feature is not yet targeted to a specific Java release but is expected to land in 2026.
Table of contents
▚ HTTP/3▚ Negotiating the HTTP Version▚ Potential Improvements▚ Ask The Architects AnythingSort: