[
https://issues.apache.org/jira/browse/HTTPCLIENT-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494934#comment-17494934
]
Oleg Kalnichevski commented on HTTPCLIENT-2205:
-----------------------------------------------
[~rschmitt] HttpClient is capable of tracking HTTP connection state (such as
the NTLM tuser identity or the security principal of an SSL private key) but
for connection pooling to work correctly with stateful connections a user
identity token must be present in the HTTP context. Having said that users
generally tend to find it difficult to set up correctly. I would like to
re-visit the whole thing in the course of 5.3 development and potentially come
up with a better solution. Any help would be appreciated, as always.
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
