Hacker News new | ask | show | jobs
by coderdd 1467 days ago
Decryping is ephemeral though. No request body gets stored, except in RAM. Malicious operators etc, well that's always a possibility, but they supposedly have controls for that. And as others noted, they are not the only players in the path of serving your data.
1 comments

The TLS handshake itself is independent of how things get stored. It takes time to set up a secure connection. There are processes in place to help reduce that time for follow up requests in a short period of time (typically within the same session) but it's still CPU time and network time. Having to do this twice (Cloudflare's SSL cert + your origin's cert) is doubling those times. It could be tens of milliseconds or even hundreds since the network is involved (round trips to your server).

> And as others noted, they are not the only players in the path of serving your data.

There are other hops in the path to serve your data but it's just moving your encrypted bytes over the wire, decryption doesn't happen in each hop.