cef network-settings
Network Settings
System network settingsThe Chromium network stack uses the system network settings so that users and administrators can control the network settings of all applications easily. The network settings include:
So far this design decision has worked well. The only network settings that some users ask for an alternative to system settings are proxy settings. For this we recently added some command-line options that allow you to run Chromium with custom proxy settings. Preference service for network settingsAlthough the system network settings have been sufficient for our network stack, eventually there will be some configuration settings specific to our network stack, so we need to have our own preference service for those settings. See also issue 266, in which some Firefox users demand that we not use the WinInet proxy settings (the de facto system proxy settings on Windows). Command-line options for proxy settingsChrome supports the following proxy-related command line arguments:
--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=<scheme>=<uri>[:<port>][;...] | <uri>[:<port>] | "direct://"
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=(<trailing_domain>|<ip-address>)[:<port>][;...]
This tells chrome to bypass any specified proxy for the given semi-colon-separated list of hosts. This flag must be used (or rather, only has an effect) in tandem with --proxy-server.
Note that trailing-domain matching doesn't require "." separators so "*google.com" will match "igoogle.com" for example.
For example,
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=<pac-file-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.
|
最新文章
- VBS操作Excel常见方法
- (转) Learning from Imbalanced Classes
- GLSL 中的光照计算
- C#中ToString和Formate格式大全
- android143 360 短信电话拦截
- TCP/IP协议原理与应用笔记19:IP分组的交付和路由选择
- Excel教程(10) - 逻辑运算符
- Java Socket应用---通信是这样练成的
- iOS pch文件创建使用,和info.plis文件路径改变,路径的设置
- centos7上安装ffmpeg
- masm6.11的BUG?
- php5.6安装redis各个版本地址集合
- Codeforces Round #423 (Div. 2, rated, based on VK Cup Finals) E. DNA Evolution 树状数组
- 【C++】C++中的函数
- 加减乘除工具类BigDecimalUtil
- 一个关于WCF调用远程链接返回405错误不允许使用此方法的问题
- java se的那些细节
- Chapter 2 Open Book——13
- 最全Android开发常用工具类
- C++面向对象程序设计的一些知识点(5)