NullReferenceException then using Elasticsearch.Net.Connection.HttpClientConnection

[maximpashuk]

I am already using version NEST 1.1.1 and Elasticsearch.Net.Connection.HttpClientConnection 1.1.1

Conditions to receive NullReferenceException:

1. EnableCompressedResponses() in settings (support for HttpClient was added in EnableCompressedResponses has no effect on HttpClient connection #947)
2. Call Refresh() method in ElasticClient

Probably this issue has some relations with previously fixed issue #562.

[Mpdreamz]

Thank you @maximpashuk for reporting this and connecting it to that refresh issue #562

We are working on redoing our complete testing infrastructure so we can get a better test matrix going with all the IConnections/Serializers as well as being more in control as to the cluster we test against during integration tests.

The way its set up now we only test the HttpConnection extensively, that needs to change.