Configuring Essentials With a Proxy Configuration Script

Overview:


Solution:

Proxy configuration scripts will work with Manager, but require the following:

• The .pac file must be hosted as application/x-ns-proxy-autoconfig MIME Type - http://marckean.wordpress.com/2010/02/09/setting-up-proxy-pac-files-in-iis7-for-proxy-use/
• If specifying the scriptLocation in the web.config such as:

<defaultProxy useDefaultCredentials="true">

     <proxy usesystemdefault="False" scriptLocation="http://pacproxy/proxy.pac" />

</defaultProxy>

You cannot include the bypassonlocal option as a proxy setting. If it is included, the proxy.pac configuration will be removed whether it is true or false. (http://blogs.msdn.com/b/rickrain/archive/2011/03/25/why-scriptlocation-may-not-work-when-pointing-to-a-proxy-script-file-in-your-application-config-file.aspx)

• Both REST and Manager Web.config should include the proxy settings in their Web.config files
• Furthermore, a couple of notes:
  • If the configured proxy for a given URL times out, it will access it directly. This is the default behavior with .NET and cannot be changed for Manager. You can however specify multiple proxys in the proxy.pac file such as:
    • return "PROXY proxyaddress1:proxyport1; PROXY proxyaddress2:proxyport2; PROXY proxyaddress3:proxyport3";
  • If you have the proxy.pac configuration setup through "Control Panel"-> "Internet options", you can use the defaultProxy tags mentioned above