org.apache.httpcomponents.client5:httpclient5-parent

This is the first ALPHA release in the 5.6 release series. It adds several features such as transport content decompression and content compression for the async transport, support for Unix sockets, experimental support for SCRAM-SHA-256 authentication scheme, and Micrometer/OTel observations & metrics.

Commons Compress, Brotli codec, and ZStd codec are optional dependencies and get wired into the execution pipeline only if present on the classpath.

Notable changes and features included in the 5.6 series:

• Unix domain socket support.

• Support for pluggable content codecs via Commons-Compress in the classic transport. (optional).

• Support for transparent content decompression and content compression with deflate, gzip, zstd (optional), and brotli (optional) codecs in the async transport.

• Micrometer/OTel observations & metrics (optinal).

• Off-lock connection disposal by the classic pooling connection manager. Experimental.

• SCRAM-SHA-256 authentication scheme (RFC 7804). Experimental.

• Request Priority support (RFC 9218). Experimental.

Compatibility notes:

• As of this version, HttpClient uses BUILTIN HostnameVerificationPolicy by default, delegating host verification to JSSE security manager. One must explicitly configure the TLS strategy to continue using the hostname verifier shipped with HttpClient.

• Five-second TCP keep-alive is now enabled by default.

This is the first GA release in the 5.5 release series. This release finalizes the 5.5 APIs and adds several experimental features and improvements, such as request multiplexing over a shared HTTP/2 connection and the Classic API facade acting as a compatibility bridge between classic I/O client services and the asynchronous message transport used internally.

Notable changes and features included in the 5.5 series:

• Improved conformance to RFC 7616 (HTTP Digest Access Authentication).

• The connection pool implementation acts as a caching facade in front of a standard managed connection pool and shares already leased connections to multiplex message exchanges over active HTTP/2 connections. Experimental.

• Extended Auth API and improved authentication protocol logic to support mutual authentication.

• The Classic API facade now acts as a compatibility bridge between the classic I/O client services (based on the standard InputStream / OutputStream model) and the asynchronous message transport used internally. This is experimental.

• HTTP/2 support for the Fluent Facade (via Classic API facade). This is experimental.

Compatibility notes:

• As of this release, HttpClient does not automatically execute redirects if the original request manually added headers that are considered sensitive.

This is the first GA release in the 5.4 release series. This release finalizes the 5.4 APIs, upgrades HttpCore to version 5.3 and improves the Public Suffix matching algorithm implementation.

IMPORTANT! The new cache entry serialization format is incompatible with earlier versions of HttpClient Cache. Persistent caches (file system based, Memcached, EhCAche with object serialization) created with any earlier version MUST be flushed and re-populated or the cache backend MUST be configured to use the old, deprecated cache entry serializer.

Notable changes and features included in the 5.4 series:

• Improved conformance to RFC 9110 (HTTP Semantics), RFC 7616 (HTTP Digest Access Authentication), RFC 2617 (’Basic’ HTTP Authentication Scheme).

• UTF-8 encoding is used by default for text where appropriate.

• Compatibility with Java Virtual Threads and Java 21 Runtime.

• Redesign and rewrite of the HTTP caching protocol layer for better efficiency and improved conformance to RFC 9111 (HTTP Caching).

• Cache control and context APIs.

• ETag APIs.

• TLS SNI and endpoint identification improvements.

• Support for RFC 2817 (Upgrading to TLS Within HTTP/1.1).

• Auth cache no longer makes use of Java serialization.

• Deprecation of ConnectionSocketFactory and LayeredConnectionSocketFactory.

• HttpContext optimization and performance improvement.

• Async cache is no longer considered experimental.

This is the first GA release in the 5.3 release series. This release finalizes the 5.3 APIs and also includes all bug fixes from the 5.2 release branch.

The 5.3 release series introduces support for the Bearer authentication scheme (RFC 6750) and deprecates NTLM and GSS-based experimental authentication schemes in favor of Basic / Bearer authentication with TLS.

Notable changes and features included in the 5.3 series:

• Introduction of the Bearer authentication scheme.

• Deprecation of the NTLM authentication scheme.

• Deprecation of the GSS-based experimental authentication schemes.

• Support for load distribution across multiple proxies.

This is a maintenance release that fixes several regressions found in release 5.2.

This is the first GA release in the 5.2 release series. This release finalizes the 5.2 APIs and corrects several defects discovered since the previous release.

Please note that 5.2 upgrades the minimal JRE level to version 8 (8u251 is required).

Please note this is likely to be the last release series with support for SPNEGO and NTLM authentication. As of version 5.3 GSS-API-based authentication schemes (Kerberos, SPNEGO) and NTLM authentication schemes are going to be deprecated and disabled by default.

Notable changes and features included in the 5.2 series:

• Upgrade to Java 8.

• Improved support for TLS upgrade and HTTP protocol upgrade (async).

• Support for H2 tunneling via HTTP/1.1 proxy.

• Conformance to RFC 7617 (The 'Basic' HTTP Authentication Scheme).

• Migration to Java 8 Time primitives in State Management and Cache APIs.

• Connection and TLS configuration on a per-route basis.

• Base64 codec based on Commons Codec replaced with JRE Base64 codec. Dependency on Commons Codec dropped.

• Optional support for BR (Brotli) decompression.

This release upgrades HttpCore to the latest 5.1 version and fixes a number of issues found since release 5.1.

This is the first GA release in the 5.1 release series.

Notable changes and features included in the 5.1 series:

• Conditional conformance with RFC 3986 (Uniform Resource Identifier (URI): Generic Syntax).

• Improved support for out of sequence response message handing by the the classic (blocking) HTTP transport.

• Improved message builders.

Please note that 5.1 is going to be the last release series compatible with Java 1.7. HttpClient will require Java 1.8 as of 5.2.

This release upgrades HttpCore to the latest version, improves conformance to RFC 7235 (Hypertext Transfer Protocol (HTTP/1.1): Authentication) and addresses a number of issues found since 5.0.2 release.

This release upgrades HttpCore to the latest version, improves conformance to RFC 7235 (Hypertext Transfer Protocol (HTTP/1.1): Authentication) and addresses a number of issues found since 5.0.1 release.

This release upgrades HttpCore to the latest version and addresses a number of issues found since 5.0 release.

This is the first stable (GA) release of HttpClient 5.0.

Notable changes and features included in the 5.0 series are:

• Support for the HTTP/2 protocol and conformance to requirements and recommendations of the latest HTTP/2 protocol specification documents (RFC 7540, RFC 7541.)

  Supported features:

  ** HPACK header compression ** Stream multiplexing (client and server) ** Flow control ** Response push ** Message trailers ** Expect-continue handshake ** Connection validation (ping) ** Application-layer protocol negotiation (ALPN) ** TLS 1.2 security features

• Improved conformance to requirements and recommendations of the latest HTTP/1.1 protocol specification documents (RFC 7230, RFC 7231.)

• New connection pool implementation with lax connection limit guarantees and better performance under higher concurrency due to absence of a global pool lock.

• Support for Reactive Streams API [http://www.reactive-streams.org/]

• Package name space changed to 'org.apache.hc.client5'.

• Maven group id changed to 'org.apache.httpcomponents.client5'.

HttpClient 5.0 releases can be co-located with earlier major versions on the same classpath due to the change in package names and Maven module coordinates.