Change Details

Gandi web forwards, which we're using to redirect people from some domain names to the adequate web page, now support HTTPS. There is a recurrent but very very slow stream of people wondering why https doesn't work on these domains, as Gandi supports it it makes sense to try to enable it. Here are the currently enabled redirects : | From | to | |------|----| | http://softwareheritage.org | https://www.softwareheritage.org | | http://sponsors.softwareheritage.org | https://www.softwareheritage.org/support/sponsors/ | | http://sponsorship.softwareheritage.org | https://www.softwareheritage.org/support/sponsors/program/ | | http://testimonials.softwareheritage.org | https://www.softwareheritage.org/support/testimonials/ | The implementation of HTTPS redirects currently needs SSL certificate access on the Gandi interface. Apparently, only @rdicosmo has access to this on `softwareheritage.org`. I also have no idea about the billing implications. All things considered, the most flexible solution very well may be putting these on a reverse-proxy that we're managing, rather than relying on Gandi.

Gandi web forwards, which we're using to redirect people from some domain names to the adequate web page, now support HTTPS. There is a recurrent but very very slow stream of people wondering why https doesn't work on the domains where we're using these forwardings. As Gandi now supports it it makes sense to try to enable it. Here are the currently enabled redirects : | From | to | |------|----| | http://softwareheritage.org | https://www.softwareheritage.org | | http://sponsors.softwareheritage.org | https://www.softwareheritage.org/support/sponsors/ | | http://sponsorship.softwareheritage.org | https://www.softwareheritage.org/support/sponsors/program/ | | http://testimonials.softwareheritage.org | https://www.softwareheritage.org/support/testimonials/ | The implementation of HTTPS redirects currently needs SSL certificate access on the Gandi interface. Apparently, only @rdicosmo has access to this on `softwareheritage.org`. I also have no idea about the billing implications. All things considered, the most flexible solution very well may be putting these on a reverse-proxy that we're managing, rather than relying on Gandi.

Gandi web forwards, which we're using to redirect people from some domain names to the adequate web page, now support HTTPS. There is a recurrent but very very slow stream of people wondering why https doesn't work on these domains,the domains where we're using these forwardings. aAs Gandi now supports it it makes sense to try to enable it. Here are the currently enabled redirects : | From | to | |------|----| | http://softwareheritage.org | https://www.softwareheritage.org | | http://sponsors.softwareheritage.org | https://www.softwareheritage.org/support/sponsors/ | | http://sponsorship.softwareheritage.org | https://www.softwareheritage.org/support/sponsors/program/ | | http://testimonials.softwareheritage.org | https://www.softwareheritage.org/support/testimonials/ | The implementation of HTTPS redirects currently needs SSL certificate access on the Gandi interface. Apparently, only @rdicosmo has access to this on `softwareheritage.org`. I also have no idea about the billing implications. All things considered, the most flexible solution very well may be putting these on a reverse-proxy that we're managing, rather than relying on Gandi.