Proxy Server Support in .NET Core

[cyberprune]

Is it possible to set a proxy server for the .NET Core client, with proxy authentication too?

I have tried setting the ConnectionPolicy.ConnectionMode to Gateway and ConnectionPolicy.ConnectionProtocol = Https, but it doesn't automatically pickup the current proxy. I can't see any way to provide a HttpClientHandler to set proxy details.

[kirankumarkolli]

@ausfeldt please look into this.

[joshiamit05]

I have the same issue - haven't found a solution yet. Is there a way this can be fixed sooner?

[mrunks]

I have the same problem at my company. Its a show stopper if I cannot programmatically set the proxy like I can in the HTTPClient class.

[AdrianSanguineti]

@cyberprune, I've managed to get Microsoft to add this as a feature in 2.2.0 of the SDK which was just released 2 days ago. The DocumentClient class now accepts an optional HttpMessageHandler parameter which will allow you set the proxy details through a HttpClientHandler.

[cyberprune]

@AdrianSanguineti thanks so much, we will give it a go in our app for development

[nulltoken]

@AdrianSanguineti From what I see, the handler has only be added to one of the ctors of the DocumentClient class.

Which means that, for instance, if I'm setting behind a corporate proxy AND willing to use a specified jsonSerializerSettings, I'm up for quite a challenging choice.

[AdrianSanguineti]

@nulltoken, by saying "willing" I assume you mean "need to". I'm not sure what the design reason for that was. Maybe @kirankumarkolli could explain? jsonSerializerSettings wasn't on my list of requirements when I asked him to add HttpMessageHandler support.

Version 3 is now available and with source, so perhaps you can address the short coming there? I do also notice that v3 of DocumentClient doesn't have HttpMessageHandler support yet either.