Skip to content

Commit a77df66

Browse files
authored
Merge pull request #79759 from kgremban/jun14-proxyhttp
IoT Edge uses http to connect to proxy
2 parents 5a54274 + 74df745 commit a77df66

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/iot-edge/how-to-configure-proxy-support.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Before you begin any of the steps in this article, you need to know your proxy U
4747

4848
Proxy URLs take the following format: **protocol**://**proxy_host**:**proxy_port**.
4949

50-
* The **protocol** is either HTTP or HTTPS. The Docker daemon can use either protocol, depending on your container registry settings, but the IoT Edge daemon and runtime containers should always use HTTPS.
50+
* The **protocol** is either HTTP or HTTPS. The Docker daemon can use either protocol, depending on your container registry settings, but the IoT Edge daemon and runtime containers should always use HTTP to connect to the proxy.
5151

5252
* The **proxy_host** is an address for the proxy server. If your proxy server requires authentication, you can provide your credentials as part of the proxy host with the following format: **user**:**password**\@**proxy_host**.
5353

@@ -245,7 +245,7 @@ With the environment variables included, your module definition should look like
245245
},
246246
"env": {
247247
"https_proxy": {
248-
"value": "https://proxy.example.com:3128"
248+
"value": "http://proxy.example.com:3128"
249249
}
250250
},
251251
"status": "running",

0 commit comments

Comments
 (0)