Applications do not always respect proxy.pac

Originator:kris
Number:rdar://28450672 Date Originated:09/23/2016
Status:3rd Party issue Resolved:03-Oct-2016 11:41 AM
Product:macOS Product Version:
Classification: Reproducible:
 
Summary:
Certain applications, Safari included, do not always respect the Automatic Proxy Configuration proxy.pac file. In our environment (50+ Macs) this file is stored locally on each system in the /Users/username/.ssh/ directory and is referenced in system preferences by the file:/// URL protocol.

Steps to Reproduce:
1. Install proxy.pac file for all network interfaces using a bash script (https://github.com/macmule/setAutomaticProxyConfigurationURL)
2. Attempt to use internal website on Safari, unable. Attempt same website in Chrome/Firefox, able to connect.

Expected Results:
Expected results would be that internal sites hosted on our internal domain would render in any browser as the proxy.pac file is referenced at the network interface level. Clicking on Proxy settings in Safari opens this setting in System Preferences, but fails to respect it.

Actual Results:
In Safari, after entering the URL and hitting Enter to engage, the progress bar will not move. Safari will eventually time out with a "Safari Can't Open the Page" error stating that "the server where the page is located isn't responding."

In Chrome/Firefox the website is nearly instantaneously loaded.

Version:
10.12 (16A323) (app store upgrade from 10.11.6)

Notes:
I have also noticed some crashing with references to the proxy.pac file in Outlook 2016. This is possibly related, but since the proxy file has nothing to do with our email servers (office365) it should read through and then bypass.

Configuration:
This has been noticed on a MacBook Pro (Retina, 13-inch, Early 2015) with macOS 10.12 (16A323)

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!