You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are using CNAME or ALIAS records for your custom domain, you’re all set and your site should be accessible over HTTPS.
jruby.org doesn't currently use MX records, in which case either of the above options are good. But if we want to leave mail functionality open as a possibility, then I'd suggest against using CNAME.
CNAME would break mail functionality for a domain. as suggested here on S.O., a good approach is to use A, ALIAS or ANAME - but not a CNAME.
Activity
sfgeorge commentedon Jul 11, 2018
⏫ Agreed, this is important.
*.gihub.io
👍 But https://jruby.org needs an SSL cert for jruby.org.sfgeorge commentedon Jul 11, 2018
According to the GitHub Blog Post, Custom domains on GitHub Pages gain support for HTTPS:
jruby.org doesn't currently use MX records, in which case either of the above options are good. But if we want to leave mail functionality open as a possibility, then I'd suggest against using CNAME.
CNAME would break mail functionality for a domain. as suggested here on S.O., a good approach is to use A, ALIAS or ANAME - but not a CNAME.
GitHub Help: Setting up an apex domain
headius commentedon Dec 2, 2018
Thanks for the tips, folks. We fixed this a couple months ago.