Open jobchong opened 6 years ago
With the deployment of keycdn and the certsimple cert there,
work. https://www.legalese.com requires an additional letsencrypt cert for keycdn, which virgil has very nicely offered to do. In the meantime, Chrome does redirect www to not-www even if the cert is only for not-www.
Dnsimple does not do https redirects: https://support.dnsimple.com/articles/redirector-https/
Why is no https redirects a problem? In most modern browsers, when something like
domain.com
is entered, the browser attempts to send the request ashttps://www.domain.com
So a request is made to
https://www.legalese.com
. However, no redirect to root athttps://legalese.com
exists, because no https redirect. So, nohttps://www.legalese.com
.Dnsimple describes how to redirect www to not-www with HTTPS at https://support.dnsimple.com/articles/redirect-heroku/#redirect-https
This requires access to the Heroku ssl deployment of our nice Legalese Pte. Ltd EV SSL cert which virgil controls. So he can fix that, or ideally transfer control of the cert deployment to clause.