Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by ploggingdev | Hacker News Reader

Parent Full thread

ploggingdev·

Do the "requests" mean page views or http requests? A single page view almost always has multiple http requests.

Github really needs to add https support for custom domains. It's 2016, https should be the default.

[Reposting my comment]

View on HN

CloudFlare supports HTTPS for GitHub Pages, would definitely recommend it as although Namecheap is pretty good CloudFlare make everything DNS, CDN and security related soo easy for $0. (I'm not affiliated with them in any way :P )

https://blog.cloudflare.com/secure-and-fast-github-pages-wit...

The route from the user's browser to Cloudflare is encrypted (https), but the route between Cloudflare's servers and github pages is only http as Github does not support https for custom domains.

User <---https---> Cloudflare <---http---> Github pages

As long as your github page has https (it does) Cloudflare can do full HTTPS all the way through, and even strict to require a valid ssl cert (which github has).

Any tips on how to configure this? I'm pretty sure my setup has the problem that ploggingdev talked about.

I acknoledged the issue given, but considered it better that the content the user is accessing was hidden for their privacy - the link between Cloudflare and GitHub is backbone-of the internet stuff and has a whole different set of risks. Would be nice to plug it.

https://support.cloudflare.com/hc/en-us/articles/200170416-W...

I don't think this is correct for GitHub Page sites that use custom domains. See [1] and [2].

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

[2]: https://github.com/isaacs/github/issues/156

Reply on news.ycombinator.com