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
These days https is considered baseline for hosting a website. In the coming months, browsers will start marking http URLs as insecure.
In the past, enabling https would require getting a certificate from a CA, which was a manual, time consuming and (sometimes) costly process. But now, there's the LetsEncrypt CA, which allows automation and is free.
If enabling https on your current hosting provider is difficult, I recommend using netlify.com. I have recently transitioned some of my sites to netlify, which supports:
deployment through git repository
custom domain such as flif.info
HTTPs over custom domain, with HSTS support
The text was updated successfully, but these errors were encountered:
These days https is considered baseline for hosting a website. In the coming months, browsers will start marking http URLs as insecure.
In the past, enabling https would require getting a certificate from a CA, which was a manual, time consuming and (sometimes) costly process. But now, there's the LetsEncrypt CA, which allows automation and is free.
If enabling https on your current hosting provider is difficult, I recommend using netlify.com. I have recently transitioned some of my sites to netlify, which supports:
The text was updated successfully, but these errors were encountered: