[
https://issues.apache.org/jira/browse/HTTPCLIENT-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494167#comment-17494167
]
Oleg Kalnichevski commented on HTTPCLIENT-2205:
-----------------------------------------------
> Our app provides services that allows to users to use their own keystores to
> make some http request. So it is necessary to set a SSLContext/keystore for
> each every request.
[~Logan007] This still makes no sense at all. What you likely want is a
different connection per different user identity, not a different SSL context
for each and every request.
> Yes BasicHttpClientConnectionManager could be used however it is efficient if
> there is some ConnectionManager that supports asynchronous http.
There is nothing stopping you from building a non-pooling async connection
manager.
Oleg
> Ability to set SSL Context and hence Keystore for every request
> ---------------------------------------------------------------
>
> Key: HTTPCLIENT-2205
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2205
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Affects Versions: 5.1, 5.1.1, 5.1.3
> Reporter: Logan
> Priority: Major
>
> With Version 4.x it easy to the SSL context and hence keystore for every
> request using the following code. How with version 5.x there is no ability to
> do this anymore. I request to enable a feature to set the SSL context (and
> hence Keystore) for every request for both synchronous and asynchronous
> clients.
> {code:java}
> SSLContext sslContext = ...
> HttpClient httpClient =
> HttpClients.custom().setSSLContext(sslContext).build();
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
