@@ -59,14 +59,14 @@ To configure the proxy settings for the Azure Stack HCI operating system, run th
59
59
Here's an example of the command usage:
60
60
61
61
```powershell
62
- Set-WinInetProxy -ProxySettingsPerUser 0 -ProxyServer http://192.168.1.250:8080 -ProxyBypass "localhost; 127.0.0.1; *.contoso.com; node1; node2; 192.168.1.*; s-cluster"
62
+ Set-WinInetProxy -ProxySettingsPerUser 0 -ProxyServer http://192.168.1.250:8080 -ProxyBypass "localhost, 127.0.0.1, *.contoso.com, node1, node2, 192.168.1.*, s-cluster"
63
63
```
64
64
65
65
### WinInet proxy bypass list string considerations
66
66
67
67
When configuring the ` WinInet ` proxy bypass list, keep the following points in mind:
68
68
69
- - Parameters must be separated with comma ` , ` or semicolon ` ; ` .
69
+ - Parameters must be separated with comma ` , ` .
70
70
- CIDR notation to bypass subnets isn't supported.
71
71
- Asterisk can be used as wildcards to bypass subnets or domain names. For example, ` 192.168.1.* ` for subnets or ` *.contoso.com ` for domain names.
72
72
- Proxy name must be specified with ` http:// ` and the port. For example, ` http://192.168.1.250:8080 ` .
@@ -83,7 +83,7 @@ When configuring the `WinInet` proxy bypass list, keep the following points in m
83
83
Current WinHTTP proxy settings:
84
84
85
85
Proxy Server(s) : http://192.168.1.250:8080
86
- Bypass List : localhost; 127.0.0.1; *. contoso.com; node1; node2; 192.168.1.*; s-cluster
86
+ Bypass List : localhost, 127.0.0.1, *. contoso.com, node1, node2, 192.168.1.*, s-cluster
87
87
88
88
PS C:\>
89
89
```
@@ -125,14 +125,14 @@ The parameters are described in the following table:
125
125
Here's an example of the command usage:
126
126
127
127
``` powershell
128
- Set-winhttpproxy -proxyserver http://192.168.1.250:8080 -BypassList "localhost; 127.0.0.1; *.contoso.com; node1; node2; 192.168.1.*; s-cluster"
128
+ Set-winhttpproxy -proxyserver http://192.168.1.250:8080 -BypassList "localhost, 127.0.0.1, *.contoso.com, node1, node2, 192.168.1.*, s-cluster"
129
129
```
130
130
131
131
### WinHTTP proxy bypass list string considerations
132
132
133
133
When configuring the ` WinHTTP ` proxy bypass list string, keep the following points in mind:
134
134
135
- - Parameters must be separated with comma ` , ` or semicolon ` ; ` .
135
+ - Parameters must be separated with comma ` , ` .
136
136
- CIDR notation to bypass subnets isn't supported.
137
137
- Asterisk can be used as wildcards to bypass subnets or domain names. For example, ` 192.168.1.* ` for subnets or ` *.contoso.com ` for domain names.
138
138
- Proxy name must be specified with ` http:// ` and the port. For example, ` http://192.168.1.250:8080 ` .
@@ -149,7 +149,7 @@ When configuring the `WinHTTP` proxy bypass list string, keep the following poin
149
149
Current WinHTTP proxy settings:
150
150
151
151
Proxy Server(s) : http://192.168.1.250:8080
152
- Bypass List : localhost; 127.0.0.1; *.contoso.com; node1; node2; 192.168.1.*; s-cluster
152
+ Bypass List : localhost, 127.0.0.1, *.contoso.com, node1, node2, 192.168.1.*, s-cluster
153
153
154
154
PS C:\>
155
155
```
0 commit comments