5 ms·
> On top of that SSL handshake for HTTPS happens at Google front ends which reduces the load on our servers. Also we can send traffic to different sets of VMs b
by Drdrdrq 10y ago
> On top of that SSL handshake for HTTPS happens at Google front ends which reduces the load on our servers. Also we can send traffic to different sets of VMs based on the URL! How cool is that?
Very cool - let's just hope Google is better at hiding contents of some random memory than Cloudflare.
- ne01 10y agoDo you operate your own CDN? If not, then basically on any CDN you need to trust them with the SSL certificates unless you serve your content over HTTP. Unless you don't use a CDN at all!
- andrewflnr 10y agoI can't tell what your point is. Thats why we don't want them exposing random bits of their memory.
- im3w1l 10y agoYou could give them a certificate that is only valid for cdn.example.com, no?
- ne01 10y agoYes. But it's best to serve your entire website (including the HTML pages) via a CDN to reduce latency.
- oh_sigh 10y agoThe person who found the Cloudflare bug in the first place is a Google employee.
- dredmorbius 10y agoAre their motives similarly aligned?