-
Notifications
You must be signed in to change notification settings - Fork 4
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
Support HTTPS (TLS) connections to project custom domains #38
Comments
This feature would have prevented a lot of inconvenience for the Rust project, where we had to set up and debug a CDN as a workaround (rust-lang/rust#13180). With the advent of Let's Encrypt, getting certs for arbitrary domains can be easily automated with minimal overhead for the domain owner. Please support HTTPS on custom domains. |
Note that this is not a new unknown issue. Eric Mill said: "Of course, the work's not done until GitHub Pages supports HTTPS for custom domains. GitHub hosts a huge number of project, personal, and conference sites that use custom domains -- including GitHub's own CodeConf site -- which all continue to put their users at risk." https://konklone.com/post/github-pages-now-sorta-supports-https-so-use-it |
AWESOME! thanks for the reminder |
GitHub supports https on their main site, and as of June 2016, GitHub supports HTTPS on github.io pages (see https://github.com/blog/2186-https-for-github-pages). And that's great!
However, if projects use their own custom domain, and serve it via GitHub project pages, then HTTPS is not currently supported. There’s a workaround, but it’s not clear that it’s really secure and it imposes additional complexities: https://developer.ubuntu.com/en/blog/2016/02/17/how-host-your-static-site-https-github-pages-and-cloudflare/. Many projects use github.io pages; a sample list is here: https://github.com/showcases/github-pages-examples
Please add support for HTTPS to project custom domains; that will complete the protection of GitHub-hosted material via HTTPS.
The text was updated successfully, but these errors were encountered: