1

I've recently installed an EV SSL cert on my server, Chrome and Firefox show a green banner and padlock denoting the EV cert is installed, but in Safari, it just shows a gray padlock... is there something extra I have to do for Safari to recognize that it's an EV cert? When I look at the certificate details in Safari it is the same certificate I see in Chrome and Firefox. I've cleared the browser cache several times and have restarted the computer. iOS Safari is showing gray as well in the title when it should be green.

Improve this question
7
  • Is Safari showing any errors or warnings related to the padlock?
    – Mike Ounsworth
    Commented Feb 17, 2016 at 21:19
  • 1
    Try running the Qualys ssl test ( ssllabs.com/ssltest ) to see if there's any potential issues with your certificate/deployment that Safari is picking up on.
    – dr jimbob
    Commented Feb 17, 2016 at 21:25
  • Potentially relevant: stackoverflow.com/questions/14845177/…
    – Mike Ounsworth
    Commented Feb 17, 2016 at 21:26
  • It would be nice if we could find a description from Apple about what the gray padlock means. My google-fu is not finding my any documentation. Maybe in Safari's Help?
    – Mike Ounsworth
    Commented Feb 17, 2016 at 21:40
  • 1
    @drjimbob The SSL test shows an "A" for the overall rating
    – CJT3
    Commented Feb 18, 2016 at 12:41

1 Answer 1

Reset to default
1

Without seeing some kind of error or warning from Safari, it's hard to tell exactly what's going on.

My best guess would be that your page contains some non-http content that Safari's not happy about [link to StackOverflow post about this].

There seem to be some other things you can do wrong in the page code that Safari won't be happy about, for example using absolute references to content rather than relative [link]

Improve this answer
1
  • Nope.. not the problem, I always use relative links for internal content. As a matter of fact, Safari is now magically showing the "green bar" that it does and I have changed nothing. My guess is it must have been a caching issue somehow even though I cleared it several times, restarted the machine, and reset the P-ram.
    – CJT3
    Commented Feb 18, 2016 at 12:44

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .