UnsupportedProductException for Net Framework 7.14.0 client to 7.14.0 server

NEST/Elasticsearch.Net version: 7.14.0

Elasticsearch version: 7.14.0

.NET runtime version: NET 4.8

Operating system version: Win10

Description of the problem including expected versus actual behavior: A clear and concise description of what the bug is.

After updating my clients to 7.14.0 I’m getting the following exception for net framework applications (net core seems to be fine). The server is on-prem and is running the latest version 7.14.0

Steps to reproduce: 1. 2. 3.

Expected behavior For the messages to be sent to a 7.14.0 server without throwing an exception.

Provide ConnectionSettings (if relevant):

Provide DebugInformation (if relevant):

Exception:

2021-08-09 15:32:03.6498 Error ElasticSearch: Error while sending log messages Exception: Elasticsearch.Net.UnsupportedProductException: The client noticed that the server is not Elasticsearch and we do not support this unknown product.
   at Elasticsearch.Net.RequestPipeline.FirstPoolUsage(SemaphoreSlim semaphore) in E:\Projects\Elastic\elasticsearch-net-copy\src\Elasticsearch.Net\Transport\Pipeline\RequestPipeline.cs:line 327
   at Elasticsearch.Net.Transport`1.Request[TResponse](HttpMethod method, String path, PostData data, IRequestParameters requestParameters) in E:\Projects\Elastic\elasticsearch-net-copy\src\Elasticsearch.Net\Transport\Transport.cs:line 65
   at Elasticsearch.Net.ElasticLowLevelClient.DoRequest[TResponse](HttpMethod method, String path, PostData data, IRequestParameters requestParameters) in E:\Projects\Elastic\elasticsearch-net-copy\src\Elasticsearch.Net\ElasticLowLevelClient.cs:line 70
   at Elasticsearch.Net.ElasticLowLevelClient.Bulk[TResponse](PostData body, BulkRequestParameters requestParameters) in E:\Projects\Elastic\elasticsearch-net-copy\src\Elasticsearch.Net\ElasticLowLevelClient.NoNamespace.cs:line 296

ServerVersion:

{
  "name" : "elastic01.ukgooddeals.local",
  "cluster_name" : "logging-prod",
  "cluster_uuid" : "MIZpBxuzTHyptLMSK1hzwQ",
  "version" : {
    "number" : "7.14.0",
    "build_flavor" : "default",
    "build_type" : "deb",
    "build_hash" : "dd5a0a2acaa2045ff9624f3729fc8a6f40835aa1",
    "build_date" : "2021-07-29T20:49:32.864135063Z",
    "build_snapshot" : false,
    "lucene_version" : "8.9.0",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

[jadanah]

No problem @stevejgordon, and thanks for the quick release.

[jadanah]

I agree OrdinalIgnoreCase would be better, my mistake. It was the proxy converting all headers to lower case as per spec https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2 so I’m pretty sure it would cause issues to all net frameworks clients running es behind a proxy.