Enforce HTTPS connections
Even with an active SSL/TLS certificate, visitors can still access resources over unsecured HTTP connections.
It is best to redirect this traffic over HTTPS, as well as ensure other resources (such as images) are also loaded over HTTPS.
Before trying to enforce HTTPS connections, make sure that your application has an active edge certificate. Otherwise, visitors will not be able to access your application at all.
Also, make sure that your SSL encryption mode is not set to Off. Otherwise, Cloudflare will redirect all visitor connections automatically to HTTP.
To make sure that your visitors do not get stuck in a redirect loop, evaluate existing redirects at your origin server and within the Cloudflare dashboard.
You should generally avoid redirects at your origin server. Not only are you likely to forget about them, but they also reduce application performance. It is much faster for Cloudflare to redirect requests before they ever reach your origin.
Make sure that your redirects within Cloudflare are not forwarding traffic to URLs starting with http.
If your application contains links or references to HTTP URLs, your visitors might see mixed content errors when accessing an HTTPS page.
To avoid these issues, enable Automatic HTTPS Rewrites and pay attention to which HTTP requests are still reaching your origin server.
If your entire application can support HTTPS traffic, enable Always Use HTTPS.
If only some parts of your application can support HTTPS traffic, do not enable Always Use HTTPS and use a single redirect to selectively perform the redirect to HTTPS. Refer to Redirect admin area requests to HTTPS for an example.