Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use HTTPS proxy in Edge Hub #697

Merged
merged 10 commits into from
Jan 10, 2019
Merged

Conversation

damonbarry
Copy link
Member

In Linux, .NET Core recognizes and honors the https_proxy environment variable when it is present in a module like Edge Agent or Edge Hub. The behavior is different in Windows, however, where the default WinInet proxy settings are used (as set via the Control Panel, or Internet Explorer) and https_proxy is ignored. This is especially a problem in RS5 nanoserver containers, which don't even expose the WinInet proxy settings.

The fix is to look for the environment variable ourselves, create a WebProxy object, and attach it to the ITransportSettings object that we pass into the SDK's ModuleClient. We technically only have to do this for Windows, but we'll do it for all platforms, for consistency.

This change updates Edge Hub. Edge Agent was updated previously (see #687). Note that for Edge Hub, we have to pass the proxy info into our own System.Net.Http.HttpClient-based DeviceScopeApiClient as well as ModuleClient.

Assert.True(((AmqpTransportSettings)expectedTransportSettings).Equals((AmqpTransportSettings)transportSettings));
case AmqpTransportSettings _:
{
var expected = (AmqpTransportSettings)expectedTransportSettings;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit:
case AmqpTransportSettings expected:

case MqttTransportSettings expected:

@damonbarry
Copy link
Member Author

@myagley I made the requested changes

@damonbarry damonbarry merged commit eb75f34 into Azure:master Jan 10, 2019
@damonbarry damonbarry deleted the proxy-in-hub branch January 10, 2019 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants