People don't realise CloudFlare is a MitM-as-a-Service.
People don't realise CloudFlare is a MitM-as-a-Service.
A HTTP post request along the wire is unencrypted.
I'm talking about a submit button not HTTPS as that just encrypts the connection session and not the data sent from say a form.
If you're using or utilising CF for something where the data is being posted to an API unless you have client side encryption anything receiving that data will be received in plain text.
Someone only needs to compromise the service worker and syphon the data.
The data from the form, HTTPS POST data is not encrypted. It's plain text encapsulated in a secure socket.
Setup a PHP page with a form and capture the $_POST. All will return in plaintext.
POST is data is sent in headers which yes are encrypted by SSL but the servers receiving will receive it in plain text.
By using third party you lose full control of the data flow encrypted or not. All it takes is one weak link in the chain and your data is screwed.
You're relying on the 3rd party infrastructure not being exploited.
If CloudFlare, any "relay" were compromised, all traffic through that would be compromised. That's everything. All your bank details, full access, it's all right there.
The selling point of SSL is nobody can read what you do between you and the final destination, except when the developers of that destination enlist CloudFlare who have a root certificate that allows them to intercept everything whether you realise or not.
We've worked on this stuff for years (this stuff being how to warn users about compromised passwords). You can go back to 2018 with our work with Troy Hunt on Pwned Passwords (https://blog.cloudflare.com/validating-leaked-passwords-with...), or our 2021 work on a privacy-preserving way of checking a password against a list of known compromised passwords (https://blog.cloudflare.com/privacy-preserving-compromised-c...).
Try implementing what CloudFlare does yourself. You will very quickly realise how it works. It's actually pretty crazy.