Currently Being ModeratedJul 26, 2012 12:05 AM (in response to David A. Gatwood)
It's using a http://.....com.au:8080 server url.
I've also hotspotted through my phone, removed the proxy settings and Safari worked fine. So this proves that it's something to do with Safari being in the copr network. What I'm not sure about is whether it's something to do with the proxy, or something else. The company blocks a lot of stuff.
Currently Being ModeratedJul 26, 2012 7:27 PM (in response to drekka)
Apple changed the valid locations where Safari can read it's proxy pac file from.
As I understand it (much help from this thread https://discussions.apple.com/message/19020620#19020620 ), Safari reads the network settings when it starts up and if a proxy pac file is defined, it reads the file.
However - and this is the important thing - it is only allowed to read it from a list of specific locations. If it's anywhere else, Safari will fail to read it (silently) and simply not work. You can validate this by looking for this error in your system logs:
27/07/12 12:59:42.243 AM sandboxd: () WebProcess(24972) deny file-read-data /Library/Internet Plug-Ins/custom-proxy.pac
This is where it gets a little tricky, in Mountain Lion the list of valid locations appear to have changed. You need to look in (and this is different from Snow Leopard and Lion)
To see the list.
In my case I created the /Library/Managed\ Preferences directory which did not exist. Copied the pac file there, set the new location in my network preferences and restarted Safari to get it to read the file.
Now everything works.MacBook Pro 17, Mac OS X (10.7.2), 16G RAM, core i7 @ 2.5Ghz
Currently Being ModeratedJul 27, 2012 2:37 AM (in response to drekka)
I'm happy you are sorted drekka, however I am not working from a .pac file. Our proxy settings are typed into the Network Settings under System Preferences. Any idea how I could solve my issue?
Currently Being ModeratedJul 27, 2012 5:19 AM (in response to DewaldvN)
Sorry DewaldvN, I was concentrating on the usage of pac files because in our network they are the only solution that works.
It's a crude solution, but you could try creating a basic pac file, putting in in /Library/Managed\ Preferences and seeing if that works.
Currently Being ModeratedJul 31, 2012 6:52 AM (in response to drekka)
Drekka, there is another way also to solve the issue
Just add the following to the file com.apple.WebProcess.sb.
Please add it below the Basic system paths and above the FIXME: or System and user preferences:
(subpath "/Library/Internet Plug-Ins")
(home-subpath "/Library/Internet Plug-Ins")
Currently Being ModeratedApr 26, 2013 8:19 AM (in response to Tim Kimpton)
Need people to do bug reports to Apple.
The way it works is that they may mark it duplicate but the more they get, then the higher it gets shifted up the ladder and a more higher priority it gets!
If we want this fixed rather than having to hack it all the time we need it reported that we want Safari and what ever frameworks it uses to respect and adhere to the settings set in the System proxy settings!