On August 22, 2016 2:50:35 PM GMT+02:00, Sachin Nikumbh <sachin.niku...@mathworks.com> wrote: >Hi Oleg, > >Thanks for your response. I had thought of using custom >HostnameVerifier. However, it only gets called if the default hostname >verification fails and that won’t work for me. We need to do the custom >verification for the server certificate when the default hostname >verification is successful as well. > >We have an existing code that uses CloseableHttpAsyncClient. We have >solved our problem by using a custom SSLIOSessionStrategy, >RegistryBuilder and PoolingNHttpClientConnectionManager. Is there any >way to use similar technique with the CloseableHttpClient? > >Thanks >Sachin >
ConnectionSocketFactory in the classic HttpClient module will give you full control over the process of socket initialization. See the stock SSL implementation for details and use it as a starting point. Oleg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
