You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hc.apache.org by ol...@apache.org on 2019/03/25 14:55:02 UTC

[httpcomponents-client] 01/02: Updated release notes for HttpClient 4.5.8 release

This is an automated email from the ASF dual-hosted git repository.

olegk pushed a commit to branch release-preparation
in repository https://gitbox.apache.org/repos/asf/httpcomponents-client.git

commit 0185d66d18398662daec486e38137b15de469a1c
Author: Oleg Kalnichevski <ol...@apache.org>
AuthorDate: Mon Mar 25 15:20:25 2019 +0100

    Updated release notes for HttpClient 4.5.8 release
---
 RELEASE_NOTES.txt | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/RELEASE_NOTES.txt b/RELEASE_NOTES.txt
index 2bc2031..685bf3b 100644
--- a/RELEASE_NOTES.txt
+++ b/RELEASE_NOTES.txt
@@ -1,3 +1,39 @@
+Release 4.5.8
+-------------------
+
+This is a maintenance release that makes request URI normalization configurable on per request basis
+and also ports several improvements in URI handling from HttpCore master.
+
+
+Changelog:
+-------------------
+
+* HTTPCLIENT-1969: Filter out weak cipher suites.
+  Contributed by Artem Smotrakov <artem.smotrakov at sap.com>
+
+* HTTPCLIENT-1968: Preserve escaped PATHSAFE characters when normalizing URI path segments.
+  Contributed by Oleg Kalnichevski <olegk at apache.org>
+
+* HTTPCLIENT-1968: URIBuilder to split path component into path segments when digesting a URI
+  (ported from HttpCore master).
+  Contributed by Oleg Kalnichevski <olegk at apache.org>
+
+* Improved cache key generation (ported from HttpCore master).
+  Contributed by Oleg Kalnichevski <olegk at apache.org>
+
+* HTTPCLIENT-1968: added utility methods to parse and format URI path segments (ported
+  from HttpCore master).
+  Contributed by Oleg Kalnichevski <olegk at apache.org>
+
+* HTTPCLIENT-1968: Make normalization of URI paths optional.
+  Contributed by Tamas Cservenak <tamas at cservenak.net>
+
+* Some well known proxies respond with Content-Length=0, when returning 304. For robustness, always use the
+  cached entity's content length, as modern browsers do.
+  Contributed by Author: Jayson Raymond <jraymond at accelerantmobile.com>
+
+
+
 Release 4.5.7
 -------------------