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 -----Original Message----- From: Oleg Kalnichevski [mailto:ol...@apache.org] Sent: Monday, August 22, 2016 5:53 AM To: HttpClient User Discussion <httpclient-users@hc.apache.org> Subject: Re: CloseableHttpClient and custom verification of SSL session On August 21, 2016 10:50:47 PM GMT+02:00, Sachin Nikumbh <saniku...@gmail.com> wrote: >Hi all, > >I am using CloseableHttpClient to support HTTPS. I need to do some >client side verification after receiving the server certificate. This >needs to happen immediately after the SSL handshake and before the >actual data is exchanged. Can someone please direct me in the right >direction? > >Thanks >Sachin Custom HostnameVerifier would be the most convenient plugin 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
