#650 always-on HTTPS for project domain

[Dan]

I’d like to see HTTPS available for https://PROJECT_NAME.sourceforge.net/ and https://PROJECT_NAME.sf.net/ and ideally both with HSTS policies of always-secure.

Relatedly, after setting up a project website URL in Project Metadata > Homepage, some project aliases currently redirect thru HTTP-only URLs, or don’t work at all.

E.g. the Arianne project has set up https://arianne-project.org/ as their homepage and I’m getting the following redirects:
Accessed URL | Result | Expected
---------- | ---------- | ------
http://arianne.sf.net/ | 301 http://arianne.sourceforge.net/ | HSTS policy of internal redirect to https://arianne.sf.net/ which 301-redirects to https://arianne-project.org/
http://arianne.sourceforge.net/ | 301 https://arianne-project.org/ | HSTS policy of internal redirect to https://arianne.sourceforge.net/ (which 301-redirects to https://arianne-project.org/)
https://arianne.sf.net/ | Connection error (Connection refused) | 301 https://arianne-project.org/
https://arianne.sourceforge.io/ | 301 http://arianne.sourceforge.net/ | 301 https://arianne-project.org/
http://arianne.sourceforge.io/ | 301 https://arianne.sourceforge.io/ | HSTS policy of internal redirect to https://arianne.sourceforge.io/ (which 301-redirects to https://arianne-project.org/ )
https://arianne.sourceforge.net/ | Connection error (Connection refused) | 301 https://arianne-project.org/

For projects that don’t redirect the homepage to an external domain, https://PROJECT_NAME.sourceforge.net/ or https://PROJECT_NAME.sf.net/ or https://PROJECT_NAME.sourceforge.io/ should all work to host the project website.

PS: the ✶.sourceforge.io cert (crt.sh) will be distrusted by Google and Mozilla from September 2018.

[Dan]

Any plan on allowing https://arianne.sf.net/ ?