> 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.
The person who found the Cloudflare bug in the first place is a Google employee.
Re:To www or not www
by dredmorbius on Sunday March 19, 2017 @01:18AM
(#13905366)
Are their motives similarly aligned?
Do 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!
Re:To www or not www
by andrewflnr on Saturday March 18, 2017 @07:06PM
(#13903968)
I can't tell what your point is. Thats why we don't want them exposing random bits of their memory.
You could give them a certificate that is only valid for cdn.example.com, no?
Our users don't need to worry about CNAME vs A records they can do what ever they want with the IP, since we don't need to change this IP there is no benefit for using a CNAME.
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?
I really think that Google's HTTP Load balancer is the hidden gem of Google Cloud.