Fortify: insecure transport risks in ES tests?

Fortify found one instance on ElasticSearchConfigTest:93, one at ElasticSearchIndexTests:78, and one instance at ElasticSearchMultiTypeIndexTest:54. These are tests so I guess we can ignore them, but it raises a different question. Can we add a test using self signed certificates to make sure HTTPS works? if it is possible, could we replace HttpClient with one that uses HTTPS?

Start with ElasticSearchConfigTest:93, ElasticSearchIndexTests:78, and ElasticSearchMultiTypeIndexTest:54, then trace how HttpClient is configured in those tests. Determine whether self-signed HTTPS certificates can be exercised and whether the client can use HTTPS. Done means the relevant tests cover HTTPS successfully without insecure transport warnings.

Written by the indexing model from the issue text.