You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
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.
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.1
Update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.1
Dec 17, 2022
renovateBot
changed the title
Update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.1
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.1
Dec 17, 2022
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.1
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.2
Nov 23, 2023
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.2
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.3
Dec 1, 2023
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.2.3
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.3
Dec 6, 2023
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.3
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.3.1
Jan 24, 2024
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.3.1
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4
Sep 19, 2024
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.1
Oct 28, 2024
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.1
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.2
Feb 2, 2025
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.2
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.3
Mar 26, 2025
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.3
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.4
Apr 24, 2025
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.4.4
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.5
May 22, 2025
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.5
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.5.1
Sep 27, 2025
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.5.1
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.5.2
Dec 19, 2025
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.5.2
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.6
Dec 20, 2025
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.6
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.6.1
Apr 19, 2026
renovateBot
changed the title
fix(deps): update dependency org.apache.httpcomponents.client5:httpclient5 to v5.6.1
fix(deps): update httpclient5 to v5.6.1
Jun 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.2→5.6.1Release Notes
apache/httpcomponents-client (org.apache.httpcomponents.client5:httpclient5)
v5.6This 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), andbrotli(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.
v5.5This 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:
request manually added headers that are considered sensitive.
v5.4This 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.
v5.3This 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.
v5.2.1This is a maintenance release that fixes several regressions found in release 5.2.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.