Discovery Without an Auto-Config File
If a proxy auto-configuration file has not been deployed on the local network, WinHttpGetProxyForUrl cannot find a proxy server. If WinHttpGetProxyForUrl fails, there are several possible fall-back strategies for obtaining a viable proxy configuration, depending on its runtime environment. These include prompting for the proxy setting through a user interface, requiring someone to store the proxy configuration in the registry using the WinHTTP "ProxyCfg.exe" utility, or using WinHttpGetIEProxyConfigForCurrentUser to check whether a proxy server is listed in Internet Explorer's settings.
It is possible that there is no proxy auto-configuration file because the client has a direct Internet connection, such as through an ISP, and does not need a proxy server.
A proxy server may be required, on the other hand, but the local network may not support WPAD. In this case, the proxy configuration must be obtained from the user or found somewhere on the client machine.
A WinHTTP-based application running in a middle-tier server environment, such as a COM+ or ASP application, should rely on a server administrator setting a default proxy configuration in the registry using the "ProxyCfg.exe" utility. This default configuration information can then be retrieved either by using the WinHttpGetDefaultProxyConfiguration function, or simply by specifying the WINHTTP_ACCESS_TYPE_PRECONFIG flag in the WinHttpOpen call.
On the other hand, a WinHTTP application running on a client desktop machine can attempt to examine Internet Explorer's proxy settings. WinHttpGetIEProxyConfigForCurrentUser fills in a caller-supplied WINHTTP_CURRENT_USER_IE_PROXY_CONFIG structure with the current user's Internet Explorer proxy settings for the current active connection (dial-up, VPN or LAN). This configuration may indicate that auto-detection is used, or it may specify a URL for a proxy auto-configuration file, or it may specify an actual proxy server to use, or it may specify a combination of the three. If this information includes a PAC URL or a proxy server, the WinHTTP application can try using those.
Build date: 10/26/2012