2 ms·
The problem with that is that the connection from CloudFlare to your server is unencrypted. Ideally you will still have SSL implemented on your own server/netw
by dasil003 9y ago
The problem with that is that the connection from CloudFlare to your server is unencrypted. Ideally you will still have SSL implemented on your own server/network even when using a CDN provides it for the public facing domain.
- chrisparton1991 9y agoYep, agreed. I only use Cloudflare's SSL for a couple of static landing page websites. For things like that, I think Cloudflare is perfect. For anything else, I use LetsEncrypt.
- johnny_reilly 9y ago> The problem with that is that the connection from CloudFlare to your server is unencrypted. Not necessarily - GitHub pages serves up HTTPS so you can be HTTPS all the way down the line
- tatersolid 9y agoCloudflare will issue you a cert from their internal CA so the POP-origin connection can be secured. But then you have to install and renew that cert on your origin. Turtles all the way down.