5

With the move to HTTPS across Stack Exchange, can the HTTPS redirection be functional?

A more minor related issue: can the redirect from the HTTP redirect directly to the HTTPS URL?

  • to turn it around... did it ever work with https? why do you expect it to work now? During the move we've rewritten all askdifferent.com links to apple.se, there are no links to askdifferent in the network anymore, only external ones, and those were never https, since it never worked. This behavior is the same of other pointer domains as well (e.g. miyodeya.com) – m0sa May 19 '17 at 9:04
4

TL;DR: This will happen as a result of mostly unrelated cleanup efforts.


To clarify our position here: there were no plans to make the redirect-only domains available over https://. They were never at any point in time supported, nor do we generate links to them - so all links in existence should be http://.

Even if they were https://, they wouldn't get the benefits of https:// anyway, since they're just 301s to the site's real domain). There's really very little reason to take on the certificate complexity and cost to add these additional domains.

Not that being said, this will eventually happen anyway for other reasons. As simply as a side-effect of us shuffling redirects between name.com servers and Cloudflare for redirects. We did this for miyodeya.com for the purposes of existing SE 1.0 links - since they ever existed, not supporting this on name.com's redirect service was causing (effectively) 404s to actual content.

We moved them to our miscellaneous Cloudflare account for the purposes of redirects, supporting https:// is only a side-effect. But, maintaining 2 ways of doing something when 1 is saner/easier (we're almost done automating this) is just silly. So the plan is to move all these domains to Cloudflare. Here's the list:

  • nothingtoinstall.com
  • seasonedadvice.com
  • crossvalidated.com
  • basicallymoney.com
  • chiphacker.com
  • brewadvice.com
  • askpatents.com
  • miyodeya.com

I don't have an exact timeline as the main dev on the sync bits for Cloudflare/page rules is currently moving and out for a little while. Roughly, I'd say in the next month or two.

  • 2
    Should be done much sooner than a month or two. Just finalizing and merging in our code to manage cloudflare redirects. github.com/StackExchange/dnscontrol/pull/119 is the PR on that, just needs a couple of safety features and I will wire up all those alias domains to work properly. – captncraig May 19 '17 at 15:55
1

I have finished automating this, and askdifferent.com redirects should be working much better than they were. I expect all of these urls to properly redirect properly over http and https(possibly pending DNS ttl expiry):

  • Excellent, thanks for the update! May I ask why the redirects are 302 over 301? – grg May 22 '17 at 19:40
  • 1
    The 302s are just temporary while we validate and roll out the automated setup for them. Will convert to 301s once we are fully confident they will work. – captncraig May 22 '17 at 19:41
0

Let's get this over to the main thread for https transition.

According to the main post we should be status: done with only chat not on https.

  • Why does this need to be moved to main meta? It only affects this site – grg May 19 '17 at 7:48
  • It doesn't need to go. It just could go. Other sites with side identities need cleanup too in all likelihood. Looks like we have an answer now, though. – bmike May 19 '17 at 22:02

You must log in to answer this question.

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