-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding https support #355
Comments
This is probably related to #307 - which might be out of date. |
Github pages doesn't support HTTPS for custom domains. (See https://help.github.com/articles/securing-your-github-pages-site-with-https/) |
Ah, right you are. |
FYI: I think this could finally be done with this announcement. GitHub is moving forward to support Maybe reopening this issue again? |
Nice! |
Any update on this issue? |
the HTTPS certificate is still flagged as insecure due to using a certificate delivered to |
To whom it may concern: https://doesmysiteneedhttps.com/ |
From a quick search and a |
So from whois, it looks like @benjchristensen, or at least he should know who does own this domain. We better find out soon because the Registry Expiry Date: 2022-01-04T01:45:54Z is fast approaching. |
I have updated the DNS records and it seems https://reactivex.io is now working. Please verify. |
Thanks Ben! This issue can probably be closed, although it doesn't by default redirect you to https. We aren't enforcing so I may create a new issue that allows us to do that. You can still navigate to the page via http if you type it in or have a link. I believe the link below either enforces it, or redirects if you don't use https. |
Closing as https://reactivex.io/ is confirmed working. I also enabled "Enforce HTTPS" on the repo and http://reactivex.io should redirect properly. |
Get free ssl certificates by following these instructions, then set up the cronjob (or equivalent task scheduler) to run the cerbot once or twice a day, and then you have free ssl 5evr, which is one more than forever.
Thanks for reading!
The text was updated successfully, but these errors were encountered: