3 ms·
Here's the thing: most website owners don't know any better, it's all up to their CDN providers, like Cloudflare, to provide adequate features for security prec
by zzzcpan 10y ago
Here's the thing: most website owners don't know any better, it's all up to their CDN providers, like Cloudflare, to provide adequate features for security preconfigurations. Don't make it a user's responsibility. At the end of the day I'm annoyed by Cloudflare, forcing me to enable javascript, not by any of their customers.
- predakanga 10y agoWhen the website owner decides to use Cloudflare in front of their site, it is absolutely their responsibility to ensure that it's configured properly. Not Cloudflare's and certainly not the user's. And for that matter, it's entirely possible that they consider this correct behaviour. They may have a poorly written dynamic RSS feed that doesn't cache for instance, and want it protected. Moreover, Cloudflare provides plenty of ways for the website owner to avoid this behaviour - the global security level can be adjusted, settings for individual endpoints can be adjusted, even settings for individual IP ranges can be adjusted. As a user, you have no idea what settings the website owner has selected; it seems rash to blame Cloudflare in that context.
- zzzcpan 10y agoThere is no one else to blame. Website owners are just people, most will never be able to understand the service and all of the implications of the configurations it provides. Cloudflare is the only one here able to do something about it, not their customers or users. I don't even know why this is a discussion. Not blaming customers and users for anything is a common sense.