5

Just coming here from the main page chrome smashed my face with a large yellow screen: "The ssl certificate is not valid for this site"

Unfortunatly I didn't have the quick though to snip it, but I got a snippet from my "omnibox", aka. navigation bar:

enter image description here

It seems that chrome doesn't like the dot between meta and scifi:

enter image description here

  • 1
    If I change the URL to https in Firefox, I get a similar warning – Izkata Aug 11 '14 at 23:36
7

This is actually valid behaviour; RFC 2818 specifies that only a single level of subdomain matching is permitted for wildcard SSL certs:

Names may contain the wildcard character * which is considered to match any single domain name component or component fragment. E.g., *.a.com matches foo.a.com but not bar.foo.a.com.

Any browser that successfully matches more than one level is therefore non-compliant.

It seems that this is a technical misconfiguration with SE itself; they shouldn't be using a single-level wildcard cert on this domain.

(Do I win a prize?)

  • 1
    Yes you win a non-rep upvote :) I hope they fix this though... maybe ima drop this link in the Tavern on Meta.. – Vogel612 Aug 11 '14 at 21:39
  • It seems the root issue is, that you may not create wildcard certs for meta.*.stackexchange.com and the like since RFC 6125 (sect. 6.4.3) – Vogel612 Aug 13 '14 at 10:13
1

Uber-Meta has some answers in stash. To make it short: Switching to full SSL is scheduled. It's supposed to happen in the memetic 6-8 weeks and meta-domains will probably be changed.

Balpha has written a short answer where he refers us to Nick Craver's Blog-Post.

There Nick elaborates the difficulties of going to HTTPS. So in short:

Known problem, in progress, keep calm and pop a beer or something ;)

You must log in to answer this question.

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