There is a bug where I see a privacy error on all meta.foo.stackexchange.com sites. For example, if I try to enter meta.retrocomputing.stackexchange.com into my browser, I get this warning: 
Can someone check this out?
-
Are you going to http:// or https:// ?– Catija StaffCommented Dec 23, 2020 at 16:19
-
meta.retrocomputing.stackexchange.com– ARI FISHERCommented Dec 23, 2020 at 16:19
-
I'm going to https://– ARI FISHERCommented Dec 23, 2020 at 16:20
-
It works with retrocomputing.meta.stackexchange.com– ARI FISHERCommented Dec 23, 2020 at 16:20
-
3Oh. Yeah. I can never remember which is the "correct" version. We switched it at some point. My understanding is that we don't support the meta.[sitename].stackexchange.com any more since we swapped the order.– Catija StaffCommented Dec 23, 2020 at 16:22
-
Could probably make this a duplicate of the announcement meta.stackexchange.com/questions/292058/…– Catija StaffCommented Dec 23, 2020 at 16:23
-
I get that.. I would think that it would be a good idea to still have it be in the certificate so the warning doesn't pop up every time someone tries to access it.– ARI FISHERCommented Dec 23, 2020 at 16:24
-
This is by design (I think). All meta URL's are now <site>.meta.stackexchange.com; any meta.<site>.stackexchange.com should redirect.– OllieCommented Dec 23, 2020 at 16:24
-
1I understand... but my possibly faulty memory is that we actually switched the order because getting the certificates would be really difficult. Doing it anyway defeats the purpose of swapping the url around.– Catija StaffCommented Dec 23, 2020 at 16:27
-
Oh, ok. I see the response and that is coorect– ARI FISHERCommented Dec 23, 2020 at 16:28
Add a comment
|