4 ms·
Honest question, this is far from my area of expertise: I get why you would put Cloudflare on a public website -- but what is the benefit of wrapping the authen
by mseebach 10y ago
Honest question, this is far from my area of expertise: I get why you would put Cloudflare on a public website -- but what is the benefit of wrapping the authenticated, dynamic parts of a website/service in Cloudflare? These are things you would want to never get cached, and, I suppose, you would want end-to-end TLS'd into your own network?
- harmkolk 10y agoCloudflare is not just a caching/CDN service, they also provide DDOS protection: https://www.cloudflare.com/ddos/ https://www.cloudflare.com/ddos/
- bkeroack 10y agoIf you put all of your services behind a reverse-proxy CDN/WAF service like CloudFlare it greatly reduces your attack surface because the public has no access to your origin IPs.
- otabdeveloper 10y agoBecause the "HTTPS everywhere or you're a dinosaur and you don't deserve to live" hysteria forced everyone to put HTTPS even in places where it doesn't belong.
- jon-wood 10y agoI'm pretty sure "in front of the API for people's bank account" is exactly the place HTTPS belongs.
- scrollaway 10y ago> put HTTPS even in places where it doesn't belong Like an online banking app?