For example, -proxy-server="direct://" will make all connections not use a proxy.
By using the special "direct://" value.
For example, -proxy-server="proxy2:8080" will use the proxy at "proxy2:8080" for all traffic.
By providing a single uri with optional port to use for all URLs.
For example, -proxy-server="http=proxy1:8080 ftp=ftpproxy" tells Microsoft Edge to use HTTP proxy "proxy1:8080" for http URLs and HTTP proxy "ftpproxy:80" for ftp URLs.
Provide a semicolon-separated mapping of list scheme to url/port pairs.
You can specify a custom proxy configuration in three ways. Tells Microsoft Edge to use a custom proxy configuration. This argument is ignored if -proxy-server is configured. Tells Microsoft Edge to try and automatically detect your proxy configuration. It overrides any other proxy settings that are provided. Tells Microsoft Edge not to use a Proxy, even if the system is otherwise configured to use one. While this may protect you from liability if the judge is sane, it may not (IANAL). If you set this value to YES, GNUnet will store content on your machine that you cannot decrypt. Setting this option to YES is highly recommended for efficiency. Microsoft Edge supports the following proxy-related command-line options. Setting this option to YES allows gnunetd to migrate data to the local machine. These command-line options correspond to the following policies in the Proxy server group: To support these scenarios, Microsoft Edge supports command-line options that you can use to configure custom proxy settings. There are scenarios where users request an alternative to using the system's default proxy settings. These settings include proxy settings, and certificate and private key stores. The Microsoft Edge network stack uses the system network settings by default. This article applies to Microsoft Edge version 77 or later.