New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redirect https://www.legalese.com to https://legalese.com #253

Open
jobchong opened this Issue Aug 14, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@jobchong
Member

jobchong commented Aug 14, 2017

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 as https://www.domain.com

So a request is made to https://www.legalese.com. However, no redirect to root at https://legalese.com exists, because no https redirect. So, no https://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.

@jobchong jobchong self-assigned this Aug 14, 2017

@jobchong

This comment has been minimized.

Member

jobchong commented Aug 26, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment