4

The Stack Exchange Data Explorer aka SEDE is not mentioned in Network-wide HTTPS: It's time.

It is not listed in any of the steps, which makes sense as it's not officially part of Stack Exchange, just an external site which is just hosted on SE domain.

Unlike SE sites, http://data.stackexchange.com is not redirecting to https://data.stackexchange.com, however since the SSL is for *.stackexchange.com data.stackexchange.com is also included and technically part of the SSL.

This means the secure version of SEDE works just fine, however it's not official. Yet.

So, my questions are:

  • Is SEDE officially secured with the same SSL as the rest of Stack Exchange?

  • Should we change links pointing to the non secure URL to the secure URL instead?

  • Related post (so the same question could be asked for the SE API). – Glorfindel Dec 14 '17 at 12:58
  • @Glorfindel good catch, well, Area 51 and StackApps are not ordinary Q&A site but integral part of SE. – Shadow Wizard Dec 14 '17 at 13:01
  • But neither is SEDE ... – Glorfindel Dec 14 '17 at 13:03
  • @Glorfindel I mean Area 51 and StackApps source code is part of SE code, while SEDE code is not, which makes it... different. – Shadow Wizard Dec 14 '17 at 13:06
  • Part of Stack Exchange's mission is to make the Internet better. Eradicating http link makes the Internet better. ;) – Helmar Dec 14 '17 at 20:31
  • @Helmar not if the site is not officially SSL enabled for some reason. – Shadow Wizard Dec 14 '17 at 23:33
2

I'm not sure if it's related to Taryn's work on this issue, but right now http://data.stackexchange.com is automatically redirecting to https://data.stackexchange.com. So it seems this is .

  • Yup, likely part of whatever fix she deployed there. :) – Shadow Wizard Oct 1 '18 at 19:43
  • Sure, I'll take credit ;) Actually this appears to have been fixed a few weeks ago, by Kyle. – Taryn Oct 1 '18 at 22:24

You must log in to answer this question.

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