[
https://issues.apache.org/jira/browse/CXF-8678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8678:
------------------------------
Description: Once Apache HttpClient5 5.2 is out, we could refactor the
[hc5/AsyncHTTPConduit.java|https://github.com/apache/cxf/pull/923/files#diff-ffdced03fe3494b30838dad9d488dd80fceb4c2f484eb9ff89fc25b80e5e1490]
to use HttpContext for TLS lookup propagation (much like 4.x does). Currently,
without context-aware settings, AsyncHTTPConduitFactory caches the client upon
first AsyncHTTPConduit creation. However, if there are more than one
AsyncHTTPConduit with different TLS settings, the client is not recreated and
as such, those TLS settings are not taken into account. (was: Once Apache
HttpClient5 5.2 is out, we could refactor the
[hc5/AsyncHTTPConduit.java|https://github.com/apache/cxf/pull/923/files#diff-ffdced03fe3494b30838dad9d488dd80fceb4c2f484eb9ff89fc25b80e5e1490]
to use HttpContext for TLS lookup propagation (much like 4.x does))
> Update to Apache HttpClient5 5.2
> --------------------------------
>
> Key: CXF-8678
> URL: https://issues.apache.org/jira/browse/CXF-8678
> Project: CXF
> Issue Type: Improvement
> Reporter: Andriy Redko
> Assignee: Andriy Redko
> Priority: Major
> Fix For: 4.0.0
>
>
> Once Apache HttpClient5 5.2 is out, we could refactor the
> [hc5/AsyncHTTPConduit.java|https://github.com/apache/cxf/pull/923/files#diff-ffdced03fe3494b30838dad9d488dd80fceb4c2f484eb9ff89fc25b80e5e1490]
> to use HttpContext for TLS lookup propagation (much like 4.x does).
> Currently, without context-aware settings, AsyncHTTPConduitFactory caches the
> client upon first AsyncHTTPConduit creation. However, if there are more than
> one AsyncHTTPConduit with different TLS settings, the client is not
> recreated and as such, those TLS settings are not taken into account.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
