6 ms·
Please don't do this. It gives the user the illusion that their connection is secure, but the connection between Cloudflare and the site is not secure. Arguably
by LethargicStud 8y ago
Please don't do this. It gives the user the illusion that their connection is secure, but the connection between Cloudflare and the site is not secure. Arguably it's better to encrypt some of the route rather than none of it, but also giving people a false sense of security comes with its own drawbacks.
- nodesocket 8y agoActually "flexible" might not be needed, "full" without strict should work. Traffic is still over TLS, but a valid named certificate is not required.
- deleted 8y ago[deleted]
- jhasse 8y agoI think the user mostly cares about his connection to anything outside his network (e.g. for public WiFis).