--no-proxy-server
This tells Chrome not to use a Proxy. It overrides any other proxy settings provided.
--proxy-auto-detect
This tells Chrome to try and automatically detect your proxy configuration. This flag is ignored if --proxy-server is also provided.
--proxy-server=
This tells Chrome to use a custom proxy configuration. You can specify a custom proxy configuration in three ways:
1) By providing a semi-colon-separated mapping of list scheme to url/port pairs.
For example, you can specify:
--proxy-server="http=foopy:80;ftp=foopy2"
to use HTTP proxy "foopy:80" for http URLs and HTTP proxy "foopy2:80" for ftp URLs.
2) By providing a single uri with optional port to use for all URLs.
For example:
--proxy-server="foopy:8080"
will use the proxy at foopy:8080 for all traffic.
3) By using the special "direct://" value.
--proxy-server="direct://" will cause all connections to not use a proxy.
--proxy-bypass-list
This tells chrome to bypass any specified proxy for the given list of hosts. This flag must be used (or rather, only has an effect) in tandem with --proxy-server.
The list of hosts is given in a comma-separated list of (
For example,
--proxy-server="foopy:8080" --proxy-bypass-list="*.google.com;*foo.com;127.0.0.1:8080"
will use the proxy server "foopy" on port 8080 for all hosts except those pointing to *.google.com, those pointing to *foo.com and those pointing to localhost on port 8080.
igoogle.com requests would still be proxied. ifoo.com requests would not be proxied since *foo, not *.foo was specified.
--proxy-pac-url=
This tells Chrome to use the PAC file at the specified URL.
For example,
--proxy-pac-url="http://wpad/windows.pac"
will tell Chrome to resolve proxy information for URL requests using the windows.pac file.
