[Elasticsearch.NET 7] Breaking change on HttpConnection - how to solve?

I am using a hack to solve some internal ssl issues (self signed certificates at dev and environments)

By updating the libraries from NEST 6.x to 7.4.0 my code is broken by a breaking change.

I am using a class derived from HttpConnection and overriding the CreateHttpClientHandler method. (Setting the ServerCertificateCustomValidationCallback property on the HttpClientHandler)

But, in the new version of the library this method is changed, it is now returning a HttpMessageHandler object. (For some reason the method is still called "CreateHttpClientHandler"....)

My question:
Is there still a way to set the ServerCertificateCustomValidationCallback on the HttpClientHandler object?

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Hi @Ankona,

Have you seen the ServerCertificateValidationCallback method on ConnectionSettings? It allows you to pass a delegate to use for certificate validation, without needing to derive your own HttpConnection.