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

81–90 of 102 posts

Re: HTTPS for GitHub Pages

#81

Post by detaro »

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…

They are advertising in a thread about GitHub pages. I'd expect private pages/unpaid open-source projects are the vast majority of users of GitHub pages.

Re: HTTPS for GitHub Pages

#82

Post by mryan »

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…

You raise an interesting point. The prices seem too high for some commenters. They are presumably capable of doing this themselves on a DO box so they do not think it is valuable enough to justify that price.

However, one of the features of their highest price ($39/month) plan is that you can use 100 custom domains. If you have 100 domains hosted on Route 53 you will be paying over $50/month for domains, at which point $39/month for the service which actually hosts your static site is entirely negligible. I am curious how many people fall in to that bucket though - it seems more likely that people will run multiple sites with few custom domains, rather than a single site with 100 custom domains.

I am planning to offer some of Netlify's services in a product I am currently building. I'm still working on the pricing model but it is likely to be based on builds per month and bandwidth/storage, rather than the actual number of sites. My cost driver is not 'how many domain names are configured in my HTTP-routing layer', but rather 'how much pressure is each site putting on my build and web servers'.

Re: HTTPS for GitHub Pages

#83

Post by narrowrail »

mryan wrote: post #82
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…

You raise an interesting point. The prices seem too high for some commenters. They are presumably capable of doing this themselves on a DO box so they do not think it is valuable enough to justify that price. However, one of the features of their highest price ($39/month) plan is that you can use 100 custom domains. If you have 100 domains hosted on Route 53 you will be paying over $50/month for domains, at which poi…

Netlify never misses an opportunity to self-promote in these SSG related threads, but AWS S3/Cloudfront/route53 is so cheap and simple for the audience that would even understand the point of Netlify, it's difficult to understand their target market. Netlify is priced like Squarespace, Wix, Weebly, etc. which are quite a bit simpler.

Re: HTTPS for GitHub Pages

#84

Post by 2bitencryption »

avyfain wrote: post #33
pfista wrote: post #24

Does anyone know if github is planning to support https for custom domains?

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

I just set up HTTPS in ten minutes using a free cloudflare account and github pages with my custom domain. You do kind of add the middleman of Cloudflare, but I'm totally okay with that.

Re: HTTPS for GitHub Pages

#85

Post by 2bitencryption »

skhaz29a wrote: post #51
pfista wrote: post #24

Does anyone know if github is planning to support https for custom domains?

I added https for my personal blog using cloudflare

Same. It took me all of ten minutes to do, with a free account. Now, if I were running some service or a huge site, I'd probably want https setup on the server side and not just use Cloudflare as an inbetween. But for a personal blog it does everything I need it to do, with zero hassle.

Re: HTTPS for GitHub Pages

#86

Post by [deleted] »

narrowrail wrote: post #83
mryan wrote: post #82

Earlier quoted context omitted.

You raise an interesting point. The prices seem too high for some commenters. They are presumably capable of doing this themselves on a DO box so they do not think it is valuable enough to justify that price. However, one of the features of their highest price ($39/month) plan is that you can use 100 custom domains. If you have 100 domains hosted on Route 53 you will be paying over $50/month for domains, at which poi…

Netlify never misses an opportunity to self-promote in these SSG related threads, but AWS S3/Cloudfront/route53 is so cheap and simple for the audience that would even understand the point of Netlify, it's difficult to understand their target market. Netlify is priced like Squarespace, Wix, Weebly, etc. which are quite a bit simpler.

[deleted]

Re: HTTPS for GitHub Pages

#87

Post by 2bitencryption »

MichaelGG wrote: post #72
manigandham wrote: post #64

Earlier quoted context omitted.

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.

https://www.benburwell.com/posts/configuring-cloudflare-univ...

Re: HTTPS for GitHub Pages

#88

Post by Sephr »

bobfunk wrote: post #41
pfista wrote: post #24

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

> It's like GitHub pages

So it's free and doesn't have quota buckets? Checks it out.

This is nothing like GitHub pages… It costs money and has quota buckets

Re: HTTPS for GitHub Pages

#89

Post by MichaelGG »

2bitencryption wrote: post #87
MichaelGG wrote: post #72

Earlier quoted context omitted.

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.

https://www.benburwell.com/posts/configuring-cloudflare-univ...

That article doesn't address what I said at all. That's showing how to disable encryption on the backend (CF to Github) by selecting "Flexible".

Looking at CF's help again and having used them a bit, there seems to be no way at all to enable full encryption (user-CF-github) with CF's non-enterprise offerings. This is because the request from CF to Github is still requested with your domain name (TLS and host header).

In order for it to work with Github's *.github.io cert, Cloudflare would need to offer an option to rewrite the request itself, not just proxy it.

Re: HTTPS for GitHub Pages

#90

Post by manigandham »

georgyo wrote: post #73
manigandham wrote: post #64

Earlier quoted context omitted.

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

You're right - the request to the origin will be encrypted but not fully validated since the host header will be different. It's still an encrypted connection though which is what the OP was asking about.
Post reply on HN