Windows' ProxyServer Value Can Be a Map

A script reads ProxyServer from Windows Internet Settings and assigns it to WebProxy.Address. It works for one machine, then fails on another whose value looks like this:

http=proxy-a.example:8080;https=proxy-b.example:8080

That is a protocol-specific configuration string, not one proxy URI. Feeding the whole value to a constructor expecting a single address changes the meaning of the input.

The https key does not by itself mean the connection to that proxy uses TLS. An ordinary HTTP proxy can carry the HTTPS destination through CONNECT.

Prefer the supported system-proxy interface for the actual destination where the client provides one. Manual proxy strings, bypass rules, automatic configuration URLs and auto-discovery are different parts of the configuration. Reading one registry value cannot reproduce all of them. If you inspect the stored map, read ProxyEnable and AutoConfigURL beside ProxyServer.

If an integration must parse a manual mapping, follow its documented format, retain the protocol association and use a real URI or endpoint parser for each selected value. Splitting every colon breaks IPv6; choosing the first entry loses the distinction above.

Keep this inside the appropriate account context. The interactive user's settings are not automatically the settings of a service running under another identity.