Does anyone know if github is planning to support https for custom domains?
I added https for my personal blog using cloudflare
HTTPS for GitHub Pages
51–60 of 102 posts
Re: HTTPS for GitHub Pages
#52Earlier quoted context omitted.
Although it doesn't validate the backend certificate.
If that's what you are talking about, you can select "Full (strict)" in the SSL options to enforce origin certificate validation. https://support.cloudflare.com/hc/en-us/articles/200170416-W...
But this doesn't work because the backend certificate is invalid (it covers *.github.io rather then example.com).
Re: HTTPS for GitHub Pages
#53Does anyone know if github is planning to support https for custom domains?
Check out https://www.netlify.com (disclaimer, I'm a co-founder). It's like GitHub pages on steroids and includes free Let's Encrypt based SSL for custom domains, can run builds from your GitHub repo with any static site generator, supports rewrite/redirect rules/proxying/form processing/password protection and much more...
Your pricing model is extraordinarily expensive.
Re: HTTPS for GitHub Pages
#54Thank you GitHub for this gift, static web sites and now forced https
Forced? You can enable and disable it in every repo's settings.
Re: HTTPS for GitHub Pages
#55Earlier quoted context omitted.
Currently, they don't have plans. just use cloudflare.
That doesn't actually create a properly encrypted connection. It only encrypts between the user and the site (at CloudFlare), not between the site and Github. Without that last hop being encrypted, you have to weigh whether this is an improvement or not.
It significantly decreases the attack surface, since most of the connection will be encrypted inside CloudFare's network or over HTTPs. Should be a clear win for most cases.
Re: HTTPS for GitHub Pages
#56Does anyone know if github is planning to support https for custom domains?
Check out https://www.netlify.com (disclaimer, I'm a co-founder). It's like GitHub pages on steroids and includes free Let's Encrypt based SSL for custom domains, can run builds from your GitHub repo with any static site generator, supports rewrite/redirect rules/proxying/form processing/password protection and much more...
I agree with the others. You can host a dynamic site on digitalocean for half the cost.
Re: HTTPS for GitHub Pages
#57Earlier quoted context omitted.
Currently, they don't have plans. just use cloudflare.
That doesn't actually create a properly encrypted connection. It only encrypts between the user and the site (at CloudFlare), not between the site and Github. Without that last hop being encrypted, you have to weigh whether this is an improvement or not.
Yes it does - this is all a setting you can choose and since Github does support HTTPS (and has for a while) you can always set it on "strict" and ensure a continuous encrypted connection on both sides of CloudFlare.
Re: HTTPS for GitHub Pages
#58Earlier quoted context omitted.
Let's Encrypt is a certificate authority and provides certificates and so it would be end-to-end. However, CloudFlare is not end-to-end unless the server already supports HTTPS.
> CloudFlare is not end-to-end unless the server already supports HTTPS. That's literally what this article is about.
HTTPS isn't supported if you're using GH Pages with a custom domain.
Re: HTTPS for GitHub Pages
#59Earlier quoted context omitted.
Check out https://www.netlify.com (disclaimer, I'm a co-founder). It's like GitHub pages on steroids and includes free Let's Encrypt based SSL for custom domains, can run builds from your GitHub repo with any static site generator, supports rewrite/redirect rules/proxying/form processing/password protection and much more...
I agree with the others. You can host a dynamic site on digitalocean for half the cost.
DO isn't in the same market as this, at least going off their websites. DO means doing all the work yourself. Netlify handles everything.
I don't think the pricing is too high. If anything, the high end is too low. It's not like they're aiming at personal sites, are they? And for a company, $39 is nothing -- plans should probably start there. (Seriously, who wants to service a customer for $7 a month?)
FWIW I've never seen or heard of Netlify before in my life.
Re: HTTPS for GitHub Pages
#60Earlier quoted context omitted.
That doesn't actually create a properly encrypted connection. It only encrypts between the user and the site (at CloudFlare), not between the site and Github. Without that last hop being encrypted, you have to weigh whether this is an improvement or not.
Yes it does - this is all a setting you can choose and since Github does support HTTPS (and has for a while) you can always set it on "strict" and ensure a continuous encrypted connection on both sides of CloudFlare.
But what certificate will Github present for your custom domain? I don't think you can tell CF to accept Github pages's cert for your own domain. They either use their own CA or don't do auth, right? At least on non-enterprise plans.