Connecting to the site over TLS presents a mismatched certificate

[csuhta]

The site serves the *.herokuapp.com certificate if you try to visit it at https://git-scm.com

[julianladisch]

https://git-scm.herokuapp.com/ works, though.

[peff]

This came up again on the git list.

According to this documentation, to get this right we have to provision an SSL endpoint at Heroku. Which makes sense, but does appear to cost $20/month.

/cc @schacon

[schacon]

Ah. This was confusing me for a bit until I realized that I never figured anyone would use git-scm.com over https since there is no state or login data stored. I suppose if you directly type it in it's broken, I just never considered that. I can either redirect https traffic or buy a cert. I'll buy a cert and see if that works at all.

[peff]

I'm in the habit of just typing https:// by default these days. Also, extensions like HTTPS Everywhere will auto-redirect. So yeah, this is probably biting a minority of users, but it would be nice in the "everything should be encrypted just because" kind of way.

[schacon]

I also can't just add the endpoint, I need to provision a cert. This may take a bit of time.

[schacon]

Sweet, looks like this works now.

[peff]

💥 Looks good from here, too. Thanks @schacon.

[csuhta]

Hooray! Thank you! 🎉