Description
Once Apache HttpClient5 5.2 is out, we could refactor the hc5/AsyncHTTPConduit.java to use HttpContext for TLS lookup propagation (much like 4.x does). Currently, without context-aware settings, AsyncHTTPConduitFactory caches the client upon first AsyncHTTPConduit connection. However, if there are more than one AsyncHTTPConduit, each with different TLS settings, the client is not recreated and as such, those TLS settings are not taken into account.
https://mvnrepository.com/artifact/org.apache.httpcomponents.client5/httpclient5/5.2
Attachments
Issue Links
- relates to
-
CXF-8667 Custom certificate alias not being used when using HC5 AsyncHTTPConduit
-
- Closed
-
-
HTTPCLIENT-2209 Pass HttpContext to AsyncClientConnectionOperator
-
- Resolved
-