Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HTTPS for GitHub Pages

github.com

Post reply on HN
Print view View original

71–80 of 102 posts

Re: HTTPS for GitHub Pages

#71

Post by Spivak »

MichaelGG wrote: post #59
jayrox wrote: post #56

Earlier quoted context omitted.

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 neve…

I think they could be much improved by allowing all the features to be modified with sliders and checkboxes with the Free/Advanced/Pro presented as presets.

Re: HTTPS for GitHub Pages

#72

Post by MichaelGG »

manigandham wrote: post #64
MichaelGG wrote: post #60

Earlier quoted context omitted.

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.

CloudFlare is what serves your custom domain. On the backend you point CloudFlare to https://username.github.io and CF will receive the wildcard certificate for *.github.io

How do you do that in CloudFlare? I didn't know you could change the host in non-enterprise versions. All I've seen is the ability to proxy request to a specific IP or CNAME.

If you CNAME your site to foo.github.com, it doesn't change the R-URI or Host header.

Re: HTTPS for GitHub Pages

#73

Post by georgyo »

manigandham wrote: post #64
MichaelGG wrote: post #60

Earlier quoted context omitted.

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.

CloudFlare is what serves your custom domain. On the backend you point CloudFlare to https://username.github.io and CF will receive the wildcard certificate for *.github.io

This is where the breakdown is. Cloudflare will get the certificate for *.github.io, however it is making the request for the custom domain. It is unable to validate the certificate.

It is impossible to enable "strict" SSL mode, because it cannot validate the certificate. And as such, a bad if able to trick cloudflare to resolve username.github.io to themselves could use any SSL certificate they choose.

This is admittedly an edge case, but in such an event, the end user would see a trusted certificate and be proxied to a bad site.

Re: HTTPS for GitHub Pages

#74

Post by MichaelGG »

Spivak wrote: post #71
MichaelGG wrote: post #59

Earlier quoted context omitted.

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 neve…

I think they could be much improved by allowing all the features to be modified with sliders and checkboxes with the Free/Advanced/Pro presented as presets.

Does that actually work? I know it's appealing to tech types, but it's confusing to people in general. They probably are better off going unlimited on a few things if they can. People are incredibly weird about usage-based pricing.

Plus it creates barriers by giving people something to bikeshed over before buying. In fact, I'd wager they're probably better off going to Unlimited on a few more things where they can, and only really focusing on the things that separate high paying customers from smaller ones.

Re: HTTPS for GitHub Pages

#75

Post by MichaelGG »

rev_bird wrote: post #62
avyfain wrote: post #33

Earlier quoted context omitted.

"HTTPS is not supported for GitHub Pages using custom domains"[1] which is annoying. [1]: https://help.github.com/articles/securing-your-github-pages-...

Custom domains would be huge for me, but I totally understand. How would they ever manage to do it? They'd either need a zillion separate entries, or the broadest wildcard cert ever.

Separate entries in what? Computers do pretty good at handling many "entries". TLS will indicate the host so they can send the right cert back.

Re: HTTPS for GitHub Pages

#76

Post by franciscop »

So now github "sorta sorta" [1] supports https:

- You CAN force HTTPS for your *.github.io site.

- You CAN use an https://yourname.github.io URL.

- You CANNOT use a custom domain name with a fully secured HTTPS connection.

[1] https://konklone.com/post/github-pages-now-sorta-supports-ht...

Re: HTTPS for GitHub Pages

#77

Post by lucaspiller »

philtar wrote: post #50
bobfunk wrote: post #41

Earlier 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 consider your pricing to be completely out of touch with reality.

What sort of price would you consider good for static site hosting? GitHub provide theirs for free as it's a loss-leader, where as this is ther main business.

Re: HTTPS for GitHub Pages

#78

Post by dadrian »

manigandham wrote: post #64
MichaelGG wrote: post #60

Earlier quoted context omitted.

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.

CloudFlare is what serves your custom domain. On the backend you point CloudFlare to https://username.github.io and CF will receive the wildcard certificate for *.github.io

That doesn't work with Github because the cert doesn't match the custom domain.

Re: HTTPS for GitHub Pages

#79

Post by lotyrin »

jayrox wrote: post #56
bobfunk wrote: post #41

Earlier 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.

Plus a lot of headaches of maintaining a machine and an OS running on that machine that cost you if you value your time. Static sites + platform = stateless.

I'd compare this service to CDNs + HTTP Object storage combos like CloudFront+S3. (Still makes this look expensive since those cost cents/GB)

Re: HTTPS for GitHub Pages

#80

Post by oakwhiz »

rev_bird wrote: post #62
avyfain wrote: post #33

Earlier quoted context omitted.

"HTTPS is not supported for GitHub Pages using custom domains"[1] which is annoying. [1]: https://help.github.com/articles/securing-your-github-pages-...

Custom domains would be huge for me, but I totally understand. How would they ever manage to do it? They'd either need a zillion separate entries, or the broadest wildcard cert ever.

Let's Encrypt?
Post reply on HN