'elasticClient.Analyze' for long string throws exception

[ArtemMironov]

Long string for Analyze when it send to ElasticSearch as url param do not analyze by ElasticSearch and returns exception.

Steps to reproduce:

1. execute query, where text.Length = 6300:
   var r = _client.Analyze(a => a.Text(text))

Expected Result:
r.IsValid = true
r.Tokens != null //and contains tokens

Actual Result:
r.IsValid = false
r.Tokens = null

r.ConnectionStatus =
{StatusCode: 0,
Method: GET,
Url: http://localhost:9200/_analyze?text=In%20order%20to%20see%20index%20with%20a%20single%20call%2C%20or%20even%20on%20_all%20the%20indices.In%20order%20to%20see%20the%20recovery&pretty=true,
Request: ,
Response:
ExceptionMessage: The underlying connection was closed: The connection was closed unexpectedly.
StackTrace: at System.Net.HttpWebRequest.GetResponse()
at Elasticsearch.Net.Connection.HttpConnection.DoSynchronousRequest(HttpWebRequest request, Byte[] data) in \NEST-master\NEST-master\src\Elasticsearch.Net\Connection\Connection.cs:line 190} Elasticsearch.Net.ElasticsearchResponse

It is GET request with very long url (I cut part of it from example). When I send the same request to ElasticSearch using 'Fiddler' as POST query with body all works correct.
Is there a way to send the same request via Nest?

[Mpdreamz]

Thanks @ArtemMironov Analyze now favors sending the text over POST instead of GET 👍

Sorry for not responding sooner! Crazy past two months.