4 ms·
"HTTPS is not supported for GitHub Pages using custom domains"[1] which is annoying. [1]: https://help.github.com/articles/securing-your-github-pages-site-with
by avyfain 10y ago
"HTTPS is not supported for GitHub Pages using custom domains"[1] which is annoying.
[1]: https://help.github.com/articles/securing-your-github-pages-site-with-https/ https://help.github.com/articles/securing-your-github-pages-...
- rev_bird 10y agoCustom 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.
- MichaelGG 10y agoSeparate entries in what? Computers do pretty good at handling many "entries". TLS will indicate the host so they can send the right cert back.
- rev_bird 10y agoSorry, I meant in an Apache config file or something.
- oakwhiz 10y agoLet's Encrypt?
- libeclipse 10y agoOr they could let users specify their own certs.
- nsgi 10y agoLots of certificates with 100 hostnames each is how CloudFlare does it.
- konklone 10y agoWordpress did this by issuing Let's Encrypt certs on demand for every domain people CNAME their way.
- 2bitencryption 10y agoI 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.