NEST: customize creation of HttpClient

jonsagara · November 25, 2020, 4:29pm

Hello,

There is a known issue with targeting net5.0 on Azure App Service and trying to connect to Elasticsearch on a virtual machine connected to via an Azure VNet. The main ticket is here:

The issue is essentially that .NET 5.0's HttpClient is trying to use IPv6 wherever it's supported. The .NET runtime's team has a suggested workaround where you force HttpClient to use IPv4:

Question: is it possible to customize NEST's creation of HttpClient instances to force it to use IPv4 sockets as described in the workaround above?

Thank you,

Jon

system · December 23, 2020, 4:30pm

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

Topic		Replies	Views
Invalid NEST response built from a unsuccessful () low level call on PUT: /indexname/_doc/888 Elasticsearch	3	1288	January 10, 2020
.NET 8 - ElasticsearchClientException: The client is unable to verify that the server is Elasticsearch due to an unsuccessful product check call Elasticsearch elastic-stack-security , docker , language-clients	1	992	January 30, 2024
Could not connect to Elasticsearch: Could not create SSL/TLS secure channel Elasticsearch language-clients	1	265	April 22, 2024
Elasticsearch 5 on Azure connecting to public IP Elasticsearch	2	904	February 17, 2017
Connection issues to ES cluster from .NET (System.Net.Sockets.SocketException) Elasticsearch	2	2011	July 5, 2017

NEST: customize creation of HttpClient

Related topics