Lines Matching refs:proxies

57 What proxies to use can be described using either:
111 proxy. HTTP proxies can proxy `http://`, `https://`, `ws://` and `wss://` URLs.
120 HTTP proxies in Chrome support the same HTTP authentiation schemes as for
138 In addition to the usual HTTP authentication methods, HTTPS proxies also
141 HTTPS proxies using HTTP/2 can offer better performance in Chrome than a
142 regular HTTP proxy due to higher connection limits (HTTP/1.1 proxies in Chrome
145 Chrome, Firefox, and Opera support HTTPS proxies; however, most older HTTP
153 proxies](http://dev.chromium.org/developers/design-documents/secure-web-proxy)
222 Although manual proxy settings are a ubiquituous way to configure proxies
233   * proxies for HTTP - A list of proxy server identifiers to use for `http://`
235   * proxies for HTTPS - A list of proxy server identifiers to use for
237   * other proxies - A list of proxy server identifiers to use for everything
249   * proxies for HTTP - *empty*
250   * proxies for HTTPS - *empty*
251   * other proxies - `http://foo:8080`
259   * proxies for HTTP - *empty*
260   * proxies for HTTPS - *empty*
261   * other proxies - `http://foo:8080`, `direct://`
269   * proxies for HTTP - `https://foo:443`
270   * proxies for HTTPS - *empty*
271   * other proxies - `socks5://mysocks:1080`
279 * The `socks=` mapping is understood more broadly as "other proxies". The
280   subsequent proxy list can include proxies of any scheme, however if the
291 * If "other proxies" is non-empty use it
292 * If "proxies for HTTPS" is non-empty use it
293 * Otherwise use "proxies for HTTP"
524   configured proxies
565 Initially, Chrome will try the proxies in order. This means first attempting
581 Chrome will first attempt to issue the request through these proxies in the
592 order for proxies to attempt will be:
596 Conceptually, _bad_ proxies are moved to the end of the list, rather than being
606 (There are some caveats for how HTTPS and QUIC proxies count failures for
612 deployments whose HTTP proxies intentionally failed certain https:// requests,
618 the caching of bad proxies). Future versions of Chrome may [remove caching
619 of bad proxies](https://bugs.chromium.org/p/chromium/issues/detail?id=936130)
630 * The "Proxy" tab will show which proxies (if any) were marked as bad at the
633   re-ordered proxy list was after taking into account bad proxies.
637 When debugging issues with bad proxies, it is also useful to reset Chrome's
638 cache of bad proxies. This can be done by clicking the "Clear bad proxies"
641 will not give feedback that the bad proxies were cleared, however capturing a
916    buttons ("Re-apply settings" and "Clear bad proxies").
955 * Were any proxies marked as bad?