Skip to main content
Question

Safari 7.0 + Bluecoat Proxy - Internet Access issues

  • December 16, 2013
  • 6 replies
  • 17 views

Forum|alt.badge.img+6

Has anyone using a Bluecoat proxy experienced internet access issues after upgrading to mavericks? For the most part, Safari is basically unable to access internet sites - but Firefox and Chrome can access these sites using the same proxy.

6 replies

Forum|alt.badge.img+8
  • Contributor
  • 117 replies
  • December 16, 2013

How do you configure proxy on clients? Auto Discover? We use Blue coat and use auto discover (wpad) but I haven't tested safari in 10.9 much yet. Will take a look...


Forum|alt.badge.img+8
  • Contributor
  • 117 replies
  • December 17, 2013

In a quick test, it looks ok for me. Is it just really slow, or what makes it almost unusable?


Forum|alt.badge.img+10
  • New Contributor
  • 11 replies
  • December 18, 2013

We do not have issues with our ProxySG and Mavericks. How is yours deployed? Inline, Transparent, Explicit? Are you doing client auth, if so is it from an exception page or Kerberos or what?


jconte
Forum|alt.badge.img+12
  • Valued Contributor
  • 131 replies
  • December 29, 2013

I am having the same issues with our BlueCoat proxies and Mavericks. OCSPD is the issue because the proxy is sending back a request for credentials and the OS isn't respecting it and not providing the credentials or prompting the users to input them.. I opened a ticket with Apple Enterprise support and they acknowledged that it is an issue. We were able to duplicate it, but the only resolution was to create a system keychain that grabs the users proxy credentials if they are stored in the keychain. Unfortunately, that doesn't work for us because we force a password change every 30 days so it would need to be running constantly along with the fact that not all of our users store the proxy credentials in the keychain.
An alternate way around this would be to allow the OCSPD user agent header unauthenticated access to the internet through the proxy. I am having the same issues with Safari and iTunes. Allowing the user agent header string works reliably and the ocspd process can only be initiated via the OS so the risk is reduced significantly.


Forum|alt.badge.img+6
  • Author
  • Contributor
  • 49 replies
  • January 2, 2014

@jconte I was able to workaround the issue by turning off OCSP and CRL in Keychain > Preferences. Thinking back, we had to do the same thing in Lion to alleviate some proxy issues. I received the same feedback from Apple Support, that product management is aware of the issue and it will be addressed in an update - hopefully soon.


Forum|alt.badge.img+9
  • Contributor
  • 66 replies
  • January 7, 2014

Turning off OCSP and CRL in the keychain prefs seems to work with Safari, but I'm still getting proxy prompts for the App Store when trying to run updates. We just received word from enterprise support that they anticipate a fix in 10.9.2.