Lines Matching full:code
5 Use the <code>chrome.experimental.proxysettings</code> module to manage Chrome's
29 <a href="#type-ProxyConfig"><code>ProxyConfig</code></a> object. Depending on
31 <a href="#type-ProxyRules"><code>ProxyRules</code></a> or a <a
32 href="#type-PacScript"><code>PacScript</code></a>.
38 A ProxyConfig object's <code>mode</code> attribute determines the overall
42 <dt><code>direct</code></dt>
43 <dd>In <code>direct</code> mode all connections are created directly, without
45 <code>ProxyConfig</code> object.</dd>
47 <dt><code>auto_detect</code></dt>
48 <dd>In <code>auto_detect</code> mode the proxy configuration is determined by
51 This mode allows no further parameters in the <code>ProxyConfig</code>
54 <dt><code>pac_script</code></dt>
55 <dd>In <code>pac_script</code> mode the proxy configuration is determined by
57 <a href="#type-PacScript"><code>PacScript</code></a> object or
58 taken literally from the <code>data</code> element specified in the
59 <a href="#type-PacScript"><code>PacScript</code></a> object.
61 <code>ProxyConfig</code> object.</dd>
63 <dt><code>fixed_servers</code></dt>
64 <dd>In <code>fixed_servers</code> mode the proxy configuration is codified in
65 a <a href="#type-ProxyRules><code>ProxyRules"><code>ProxyRules</code></a>
67 Besides this, the <code>fixed_servers</code> mode allows no further parameters
68 in the <code>ProxyConfig</code> object.</dd>
70 <dt><code>system</code></dt>
71 <dd>In <code>system</code> mode the proxy configuration is taken from the
73 <code>ProxyConfig</code> object. Note that the <code>system</code> mode is
83 The <a href="#type-ProxyRules"><code>ProxyRules</code></a> object can contain
84 either a <code>singleProxy</code> attribute or a subset of
85 <code>proxyForHttp</code>, <code>proxyForHttps</code>, <code>proxyForFtp</code>,
86 and <code>fallbackProxy</code>.
95 HTTPS or FTP, the <code>fallbackProxy</code> is used. If no
96 <code>fallbackProxy</code> is specified, traffic is sent directly without a
104 <a href="#type-ProxyServer"><code>ProxyServer</code></a> object. The connection
105 to the proxy server (defined by the <code>host</code> attribute) uses the
106 protocol defined in the <code>scheme</code> attribute. If no <code>scheme</code>
107 is specified, the proxy connection defaults to <code>http</code>.
111 If no <code>port</code> is defined in a
112 <a href="#type-ProxyServer"><code>ProxyServer</code></a> object, the port is
127 <code>bypassList</code>. This list may contain the following entries:
129 <dt><code>[<em><scheme></em>://]<em><host-pattern></em>[:<em><port></em>]</code></dt>
131 Examples: <code>"foobar.com", "*foobar.com", "*.foobar.com", "*foobar.com:99",
132 "https://x.*.y.com:99"</code></dd>
134 <dt><code>[<em><scheme></em>://]<em><ip-literal></em>[:<em><port></em>]</code></dt>
140 Examples: <code>"127.0.1", "[0:0::1]", "[::1]", "http://[::1]:99"</code></dd>
142 <dt><code><em><ip-literal></em>/<em><prefix-length-in-bits></em></code></dt>
145 Examples: <code>"192.168.1.1/16", "fefe:13::abc/33"</code></dd>
147 <dt><code><local></code></dt>
150 Example: <code>"<local>"</code></dd>
204 The following code sets a SOCKS 5 proxy for HTTP connections to all servers but
226 The following code sets a custom pac script.
256 Note that the <code>value</code> object passed to <code>set()</code> is not
257 identical to the <code>value</code> object passed to callback function of
258 <code>get()</code>. The latter will contain a <code>rules.httpProxy.port</code>
