[
https://issues.apache.org/jira/browse/HTTPCLIENT-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021323#comment-17021323
]
Oleg Kalnichevski commented on HTTPCLIENT-2047:
-----------------------------------------------
[~mglazer] You do have a legitimate reason to be upset as we have indeed been
abusing the stable 4.5.x release series by including new small features and
making behavioral changes in patch releases. This should stop once 5.0 GA has
been released.
I will look into this issue tomorrow.
Oleg
> Regression in default HTTP Client construction for non-public hostnames
> -----------------------------------------------------------------------
>
> Key: HTTPCLIENT-2047
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2047
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.5.11
> Reporter: Mike
> Priority: Major
>
> I believe that the result of:
>
> https://github.com/apache/httpcomponents-client/commit/b184b244ad9342a384ba87f48c6b48805a3b0f1f
> and:
> https://github.com/apache/httpcomponents-client/commit/e0416f07c344929699a2bc303eb3a049c62bd979
>
> Caused a regression which prevents non-public hostnames from validating,
> resulting in errors like (I have redacted hostnames as possible):
> {code:java}
> Certificate for <hostname-workspace-1.ops.domain.local> doesn't match any of
> the subject alternative names: [user-id-60662,
> hostname-workspace-1.ops.domain.local, 127.0.0.1, 10.2.243.75]
> {code}
> This is because the default value of {{ICANN}} is now supplied to the
> {{PublicSuffixMatcher}}, which causes it to *only* accept publicly accessible
> hostnames now (or so it seems).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
