[Sorry, Tomas, I just realized that earlier I replied only to you rather
than to the whole list.]
There is some Debian blessing of backports.org. When visiting the
Debian webserver over http and asking for www.backports.org, the Debian
webserver redirects the visitor to https://backports.debian.org/.
It doesn't seem that there should be a difference in behavior between
http://www.backports.org/ and https://www.backports.org/, but as it is,
one works perfectly and the other fails spectacularly.
I see the options as:
a) Let backports.org die, which is mostly what you suggest. Shouldn't
the Debian webserver should have any backports.org configuration removed
from it? I believe would mean that visitors to
http://www.backports.org/ will end up getting the Debian homepage. The
owner of backports.org should be contacted so the domain could be
removed, which I'd be glad to attempt.
b) Configure the Debian webserver to acquire a certificate from Let's
Encrypt for www.backports.org and configure it to redirect visitors to
backports.debian.org just as the http:// version does.
c) Leave things as they are, where http:// works and https:// doesn't.
I just thought this was a weird situation. If you like it the way it
is, it's fine by me.
Thanks for your work on the Debian website!
-Xan
