Cross-posted at https://github.com/isaacs/github/issues/1675, hopefully this can get some more visibility...
Just to demonstrate how common this issue is in practice, I've compiled a list of popular websites that are broken due to GitHub Pages incomplete implementation:
Hi guys, this is march 2020 and I am still having this issue, why havn't Github team responded yet?
Finally found a workaround to this today!
What I did was
Now it works properly for me.
@miesmandoki You just fixed it temporarily, because it already created the SSL certificate for salt.dev (without the www), and by switching it now also created the SSL certificate for www.salt.dev, but it will only renew the latter, so when the SSL certificates expires, you'll have the same problem
Are you sure?
If that's the case - then all I'd need to do is switch it back and forth once every three months to renew the certificates, correct?
If that's all it takes and the certificate is still available, this definitely seems like something GitHub should go ahead and implement...
I got one of the new .app TLDs that went live today, and I am trying to point it to Github pages. I want the default URL to be without the www (host: @) and for the www to redirect to the default. I have set the domain without www in my pages repo settings, enabled https, and done the A and CNAME records in my DNS.
The A record is working fine, it loads my site with no www. The CNAME for www is causing an issue with the SSL certificate though. If I open the site in Edge, postman, curl, etc, it works fine; however, .app requires HTTPS and Chrome knows that, so it doesn't even bother trying http and goes straight to the HTTPS version when you type www. This gets an error because Github returns the github.com certificate, and not my own.
Is there a fix for this?