1.0 Upgrade Broke "localhost.fiddler" Connections

[andkvo]

I have the development copy of my app using "localhost.fiddler" to connect to elastic search through Fiddler to inspect the messages. After yesterday's upgrade, it's no longer working.

The connection times out with the following exception:

System.Net.WebException was unhandled by user code
HResult=-2146233079
Message=Unable to connect to the remote server
Source=System
StackTrace:
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Elasticsearch.Net.Connection.HttpConnection.DoSynchronousRequest(HttpWebRequest request, Byte[] data, IRequestConfiguration requestSpecificConfig) in c:\projects\elasticsearch-net\src\Elasticsearch.Net\Connection\HttpConnection.cs:line 220
at Elasticsearch.Net.Connection.HttpConnection.BodyRequest(Uri uri, Byte[] data, String method, IRequestConfiguration requestSpecificConfig) in c:\projects\elasticsearch-net\src\Elasticsearch.Net\Connection\HttpConnection.cs:line 92
at Elasticsearch.Net.Connection.HttpConnection.PutSync(Uri uri, Byte[] data, IRequestConfiguration requestSpecificConfig) in c:\projects\elasticsearch-net\src\Elasticsearch.Net\Connection\HttpConnection.cs:line 71
at Elasticsearch.Net.Connection.Transport.CallInToConnection[T](TransportRequestState1 requestState) in c:\projects\elasticsearch-net\src\Elasticsearch.Net\Connection\Transport.cs:line 411 at Elasticsearch.Net.Connection.Transport.DoRequest[T](TransportRequestState1 requestState) in c:\projects\elasticsearch-net\src\Elasticsearch.Net\Connection\Transport.cs:line 376
at Elasticsearch.Net.Connection.Transport.DoRequest[T](String method, String path, Object data, IRequestParameters requestParameters) in c:\projects\elasticsearch-net\src\Elasticsearch.Net\Connection\Transport.cs:line 309
at Elasticsearch.Net.ElasticsearchClient.DoRequest[T](String method, String path, Object data, IRequestParameters requestParameters) in c:\projects\elasticsearch-net\src\Elasticsearch.Net\ElasticsearchClient.cs:line 56
at Elasticsearch.Net.ElasticsearchClient.IndicesPutMapping[T](String index, String type, Object body, Func2 requestParameters) in c:\projects\elasticsearch-net\src\Elasticsearch.Net\ElasticsearchClient.Generated.cs:line 17963 at Nest.RawDispatch.IndicesPutMappingDispatch[T](ElasticsearchPathInfo1 pathInfo, Object body) in c:\projects\elasticsearch-net\src\Nest\RawDispatch.generated.cs:line 2074
at Nest.ElasticClient.b__1db(ElasticsearchPathInfo1 p, IPutMappingRequest d) in c:\projects\elasticsearch-net\src\Nest\ElasticClient-MappingType.cs:line 31 at Nest.ElasticClient.Dispatch[D,Q,R](D descriptor, Func3 dispatch) in c:\projects\elasticsearch-net\src\Nest\ElasticClient.cs:line 81
at Nest.ElasticClient.Map(IPutMappingRequest putMappingRequest) in c:\projects\elasticsearch-net\src\Nest\ElasticClient-MappingType.cs:line 23
at Nest.ElasticClient.Map[T](Func`2 mappingSelector) in c:\projects\elasticsearch-net\src\Nest\ElasticClient-MappingType.cs:line 17

[gmarz]

Hey @DarthGregarious, we disable automatic proxy detection by default in 1.0, which I believe is what's causing your issue. See #809 for some background on why we made this change.

Try enabling automatic proxy detection:

var settings = new ConnectionSettings(...);
settings.DisableAutomaticProxyDetection(false);

Let me know if that resolves it for you.

[andkvo]

That's exactly what it was. Thanks very much!

[billumina]

Thank you!!!