Please petition GitHub to support HTTPS on GitHub pages

This is a little weird to me, because it&#x27;s so easy to host your site a multitude of different ways. The notable thing about GH is its free, which makes complaining about it not having the one feature you want so odd. If you want that feature, pay the buck or two it will cost to host your site on CloudFront with something like Stout [1].<p>1: <a href="http:&#x2F;&#x2F;stout.is" rel="nofollow">http:&#x2F;&#x2F;stout.is</a>

You can use CloudFlare with a custom domain in front of Github Pages. It works. I do this for <a href="https:&#x2F;&#x2F;github.com&#x2F;leighmcculloch&#x2F;5tweets.com" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;leighmcculloch&#x2F;5tweets.com</a> which you can see SSL&#x27;d at <a href="https:&#x2F;&#x2F;5tweets.com" rel="nofollow">https:&#x2F;&#x2F;5tweets.com</a>.

FYI, when Let&#x27;s Encrypt goes public in a week, you&#x27;ll be able to get free certs without having to install anything by using <a href="https:&#x2F;&#x2F;gethttpsforfree.com" rel="nofollow">https:&#x2F;&#x2F;gethttpsforfree.com</a><p>Fun fact, the website is just a reverse proxied github static page: <a href="https:&#x2F;&#x2F;diafygi.github.io&#x2F;gethttpsforfree" rel="nofollow">https:&#x2F;&#x2F;diafygi.github.io&#x2F;gethttpsforfree</a>

I&#x27;d love to see SSL support on custom domains as well, but I know there are a couple of reasons why it hasn&#x27;t happened already:<p>1. GitHub Pages likely isn&#x27;t a core focus for GitHub, however useful it may be<p>2. GitHub Pages is currently completely interface-less, relying only on an automated build system running each site through Jekyll and deploying it. In order to support custom certificates, they would need to build an interface for certificate uploading&#x2F;maintenance (and of course putting the certs &amp; keys into the repo, like the current CNAME system, won&#x27;t work).

+1<p>But are you guys seriously going to spam github&#x2F;contact or support@github.com ?<p>Because if that was my inbox. I&#x27;d be pissed looking at thousands of emails that contain the same body.

I agree with imbriaco&#x27;s sentiment from the linked discussion - using a CDN or some other host that supports SSL to host your static site is a good solution. I recently migrated my GitHub pages site to Amazon S3 and Cloudfront. I had to buy a cheap Comodo SSL certificate and upload it to AWS to get it working with my custom domain, but the documentation[1] was good enough that it didn&#x27;t take me very long at all.<p>[1] <a href="http:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;AmazonCloudFront&#x2F;latest&#x2F;DeveloperGuide&#x2F;SecureConnections.html#CNAMEsAndHTTPS" rel="nofollow">http:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;AmazonCloudFront&#x2F;latest&#x2F;Developer...</a>

What&#x27;s missing in all that is that they are talking about HTTPS for custom domains, <i>username</i>.github.io supports HTTPS already.

Maybe let people star a dedicated repo instead of sending an email to github.

While GitHub has a free account, it gets quite expensive when you start paying. And GitHub Pages is a complementary add-on and many of us stayed on GitHub because of nice things like this. I do agree that it isn&#x27;t their core focus and that people could host their stuff somewhere else for cheap.<p>However there is something to be said about making encrypted connections the standard. Chrome and Firefox will only support encrypted HTTP 2.0 connections. So if GitHub Pages does not provide HTTPS for custom domains, then it won&#x27;t support HTTP 2.0. Adding HTTPS support is also the right thing to do given the recent attacks on privacy.<p>Yes, GitHub Pages is a free add-on that isn&#x27;t their competency, but in my opinion they should either drop it completely, or support HTTPS. Because otherwise they are keeping the web back due to their popularity.

Yeah, and please send me a free flying car while you are at it.<p>Obviously everybody would like that, but it&#x27;s not as easy as it seams. As github pages, technically are virtual domains, they share the same ip with many other pages, if you want to support https, you need to serve either each page on a different ip (not free), or they need a to configure multidomain ssls (which everytime they need to add a new domain, that means they have to reset the certificate for the other domains on the same ip), and I think there is a limit on the number of domains that can share the same ip - citation needed - . And all of this for free.<p>Want SSL on gh pages, setup a proxy infront of gh pages.

Its quite a co-incidence that I scouted for an answer for this today while I was setting up SSL for my gh-pages. As already pointed out by some comments, its not quite as simple as we think it is to have GitHub extend SSL for its pages. Its for the same reason that Tumblr doesn&#x27;t allow SSL support for custom domain either. IMHO, CloudFlare is probably the simplest workaround to get SSL enabled for your gh-pages. Link on how to <a href="https:&#x2F;&#x2F;me.net.nz&#x2F;blog&#x2F;github-pages-secure-with-cloudflare&#x2F;" rel="nofollow">https:&#x2F;&#x2F;me.net.nz&#x2F;blog&#x2F;github-pages-secure-with-cloudflare&#x2F;</a>

What&#x27;s missing is, why? It&#x27;s a static site, so you won&#x27;t get any real privacy about what you&#x27;re reading. If you have binaries to distribute, you have other features for releasing them that let you use TLS.

I also have my personal website on GH pages + Cloudflare. If it is for a static web site I think it is ok, and thanks to both companies that gives us this service for free.<p>If you pretend more you can pay and use AWS or some other service.

Of note guys there&#x27;s a little ! icon button in the top of the page to report this gist. It&#x27;s basically encouraging spam and as everyone has pointed out, is likely not technically sound.

Worth noting: https works on yourname.neocities.org.

I add SSL through a proxy to GitHub pages.

Been wanting built in ssl forever.

Isn&#x27;t Github Pages hosted on S3? That would explain the lack of TLS on custom domains.<p>Anyway, this is a very major security flaw. Lots of software uses Github pages for the project website. If you put a download link on an unsecure page, you are putting all your customers st risk.