ProxyOverrideRules

Configures rules that select which proxy the browser uses based on the destination URL and specific network conditions. This policy takes precedence over the ProxySettings policy, the chrome.proxy extension API, and manual user settings. If no rules in this policy match, the browser falls back to the settings defined in ProxySettings. The browser evaluates entries in the ProxyOverrideRules list in sequence. A rule is applied only if all of the following criteria are met: * Match: At least one URL pattern in DestinationMatchers is matched. * Exclude: No URL patterns in ExcludeDestinationMatchers are matched. * Conditions: If Conditions is specified, all listed conditions must be satisfied. If unset, this requirement is ignored. URL patterns for matchers are documented at https://chromium.googlesource.com/chromium/src/+/HEAD/net/docs/proxy.md#proxy-config-url-patterns. The ProxyList field defines a failover list. The first reachable entry is used; invalid entries are ignored. You can use PAC-style strings or URL-like specifiers: PAC-style strings: * DIRECT * PROXY host:port * HTTPS host:port * SOCKS4 host:port * SOCKS5 host:port URL-like specifiers: * http://host:port * https://host:port * socks4://host:port * socks5://host:port The DnsProbe condition checks if a Host resolves to an IP address. * Supports hostnames (e.g., example.com) or URI-style strings (e.g., https://example.com:123). Using a secure scheme (https) may trigger an HTTPS record request (see RFC 9460). * Set to "resolved" to meet the condition upon successful resolution, or "not_found" to meet the condition if resolution fails. The application of this policy on managed devices is influenced by the EnableProxyOverrideRulesForAllUsers machine-level policy on the platforms where it is supported. By default, it prevents the usage of override rules configured by unaffiliated users.