When you run Project Server Setup, proxy settings are automatically configured for your Project Server installation. If you need to change or update the proxy server configuration, you can use the WinHTTP proxy configuration tool (Proxycfg.exe), which is installed on the server when you run Project Server Setup.
To run Proxycfg.exe
- On the computer on which Project Server 2003 is installed, click Start, click Run, type cmd, and then click OK.
- Browse to the \Program Files\Microsoft Office Project Server 2003\Bin folder, and then run Proxycfg.exe by using the parameters listed in the following tables.
- Restart Internet Information Services (IIS).
Note New or updated information for Proxycfg.exe will not take effect until Internet Information Services is restarted.
WinHTTP Proxy Configuration Tool Options
The following table lists and describes the options for Proxycfg.exe.
| Option |
Description |
| Proxycfg |
This command displays the current WinHTTP proxy settings. |
| proxycfg –d |
This command specifies that all HTTP and HTTPS servers should be accessed directly. Use this command if there is no proxy server. |
| proxycfg –p proxy–server–list optional–bypass–list |
This command specifies one or more proxy servers, and an optional list of hosts that should be accessed directly. If a proxy server is not specified for a given protocol and that server is not in the bypass list, the –p option specifies that the server cannot be accessed at all. |
| proxycfg –d –p proxy–server–list optional–bypass–list |
This command specifies one or more proxy servers, and an optional list of hosts that should be accessed directly. If a proxy server is not specified for the given protocol, the –d option specifies that the server should be accessed directly instead. |
| proxycfg –u |
This command imports the Internet Explorer proxy settings of the current user. WinHTTP does not support auto–discovery and configuration script–based proxy settings. |
The following table describes how to use both the proxy–server–list and optional–bypass–list parameters.
| Parameter |
Description |
| proxy–server–list |
Proxies are specified in a space–delimited string. The proxy listings can contain the port number used to access the proxy.
Proxy servers can be listed to use a specific protocol. The valid protocols are HTTP or HTTPS. The syntax for a proxy listing that specifies a protocol is: protocol=protocol://proxyNname
where protocol is either http or https and proxyName is the name of the proxy server. For example, the string http=http://proxy_name:80 specifies that the protocol is HTTP, the name of the proxy server is proxy_name, and the port number for this server is 80. An example of a proxy listing that specifies the HTTPS protocol is:
https=https://proxyName
If the proxy server uses the default port number for the protocol, the port number can be omitted.
If a proxyName is listed by itself, the Proxycfg.exe tool uses that proxy as the default proxy for any protocols that do not have a proxy specified. For example, the listing http=http://proxyName other_proxy
specifies using the proxyName server for any HTTP operations and the other_proxy server for any HTTPS operations.
|
| optional–bypass–list |
This list contains host names or IP addresses that are locally known.
This list can contain wildcards, "*", that cause the application to bypass the proxy server for addresses that fit the specified pattern. For example, both *.example.com and *.org are acceptable wildcard patterns. Wildcard characters must be the left–most characters in the list, so myserver.* is not supported.
To list multiple addresses and host names, enclose them in quotes and separate them with semicolons. If the <local> macro is specified, the function bypasses any host name that does not contain a period.
|
Examples
The following is the most common command used with the Proxycfg.exe tool. This command specifies the use of the proxy server named myproxy to access both HTTP and HTTPS servers, and also to bypass any host names that do not contain a period. In this case, the –d option has no effect.
proxycfg –d –p myproxy "<local>"
Compare the previous command to the following command, which specifies use of the proxy server named myproxy to access both HTTP and HTTPS servers, and to not bypass any servers.
proxycfg –p myproxy
The following is an example of a more complex command used by the Proxycfg.exe tool. This command specifies the use of the proxy server named http_proxy to access HTTP servers and the server named https_proxy to access HTTPS servers. This command also specifies that local intranet sites (for example, host names that do not contain a period) and any site in the *.example.com domain bypass the proxy.
proxycfg –p "http=http_proxy https=https_proxy" "<local>;*.example.com"
