HTTPS with rtfd.org

[buhtz]

e.g.
This work
http://backintime.rtfd.org/
but it's HTTPS version doesn't work because of in invalid certificate
https://backintime.rtfd.org/

And IMO http://backintime.rtfd.org/ should not be redirected to http://backintime.readthedocs.io/en/latest/ but to https://backintime.readthedocs.io/en/latest/

[davidfischer]

The main chunk of this looks like a dupe of #328.

The second half of this seems like a good improvement.

Edited for clarity.

[jab]

You could fix this issue right now by making http://foo.readthedocs.io redirect to https://foo.readthedocs.io. Isn't it worth doing that anyway?

It would mean an extra redirect in the foo.rtfd.org case, but the end result would be the same, and you could tackle the 1-step redirect from rtfd.org independently. This would be strictly better than the current behavior, isn't blocked by #328, and seems like a ~1-line change, no?

[jab]

Just opened #3874 to track this independently.

[jab]

Looks like https://foo.rtfd.io is working now! 🎉
Close?

[davidfischer]

You could fix this issue right now by making http://foo.readthedocs.io redirect to https://foo.readthedocs.io. Isn't it worth doing that anyway?

Yes. We deployed that today.

Close?

We can close it. I'm working on getting a wildcard cert for *.rtfd.org as well although I think fewer people are using that.

[davidfischer]

There is now a cert for *.rtfd.org as well.