[
https://issues.apache.org/jira/browse/GERONIMO-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551162
]
Sangjin Lee commented on GERONIMO-3703:
---------------------------------------
One idea would be to allow callers to pass in SSLContext. One thing to think
about is whether we want to make it part of an AsyncHttpClient instance or pass
in SSLContext as part of a sendRequest() call.
I think Jeff was talking about using a single instance of AsyncHttpClient for
various different hosts, and I think it makes sense. If we want to preserve
that ability, then making SSLContext part of AsyncHttpClient (which it is
today) may not be a good idea. Maybe we should pass it in explicitly when we
call sendRequest()?
> should allow custom SSL context for AsyncHttpClient
> ---------------------------------------------------
>
> Key: GERONIMO-3703
> URL: https://issues.apache.org/jira/browse/GERONIMO-3703
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: AsyncHttpClient
> Affects Versions: 1.x
> Reporter: Sangjin Lee
> Priority: Critical
>
> Currently the SSLContext that's used to do https cannot be configured or
> customized. One needs to be able to create and pass in custom SSLContext to
> be able to use its own cert directory, keystore file, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
