Possible Duplicate:
Better HTTPS support for Stack Exchange sites

I usually visit Stackoverflow through https. Since a few days, Safari will warn me that it can't verify the identity of the server because the certificate is invalid. A little experiment just told me that Firefox is giving the same warning.

A similar question has been asked in 2009, but then the certificate was not trusted rather than simply invalid.

What is going on, and when can we expect it to be fixed?


The warning is given because the certificate used is a wildcard cert for *.stackexchange.com sites only, and stackoverflow.com doesn't match that domain name (obviously).

Otherwise the cert looks in perfect order.

My guess is that using https://stackoverflow.com isn't officially supported; it just happens to work because the front-end webserver acts a virtual host server for all stackexchange.com sites, including those that do support HTTPS such as https://openid.stackexchange.com/.

  • 1
    I would like to know whether it's true that using stackoverflow over https is unsupported. And if so, why it has worked for so long.
    – Julian
    Aug 22 '12 at 10:32
  • 3
    @Julian It's not supported. And I've heard of people seeing this exact warning before, so I'm not sure why you weren't seeing it, but it's not new Aug 22 '12 at 12:12
  • Thank you for affirming that.
    – Julian
    Aug 22 '12 at 18:52
  • 1
    @Julian: See my answer on another question for why this happens.
    – animuson StaffMod
    Aug 24 '12 at 3:02

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