To www or not www

Re:To www or not www by Drdrdrq on Saturday March 18, 2017 @05:32PM (#13903625)

> 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.

[ Parent | on HN ]

Re:To www or not www by oh_sigh on Sunday March 19, 2017 @12:51AM (#13905252)

The person who found the Cloudflare bug in the first place is a Google employee.

[ Parent | on HN ]

Re:To www or not www by dredmorbius on Sunday March 19, 2017 @01:18AM (#13905366)

Are their motives similarly aligned?

[ Parent | on HN ]

Re:To www or not www by ne01 on Saturday March 18, 2017 @06:45PM (#13903879)

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!

[ Parent | on HN ]

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.

[ Parent | on HN ]

Re:To www or not www by im3w1l on Saturday March 18, 2017 @09:13PM (#13904534)

You could give them a certificate that is only valid for cdn.example.com, no?

[ Parent | on HN ]

Re:To www or not www by ne01 on Saturday March 18, 2017 @10:35PM (#13904829)

Yes. But it's best to serve your entire website (including the HTML pages) via a CDN to reduce latency.

[ Parent | on HN ]