MeowerMisfit817@lemmy.world to Out of the loop@lemmy.worldEnglish · 3 days agoWhy are people hating on Cloudflare?message-squaremessage-square48fedilinkarrow-up144arrow-down14
arrow-up140arrow-down1message-squareWhy are people hating on Cloudflare?MeowerMisfit817@lemmy.world to Out of the loop@lemmy.worldEnglish · 3 days agomessage-square48fedilink
minus-squareNekuSoul@lemmy.nekusoul.delinkfedilinkarrow-up6·3 days ago Some routing instance in between your users and your server might. Although that should only be possible if the user has a hijacked client or you’re not using HTTPS. Or am I forgetting something?
minus-squarehitmyspot@aussie.zonelinkfedilinkarrow-up7·3 days agoCloud flare issue certificates on your behalf when they cache. They also have nameservers. However, I assume that is only for their customers.
minus-squareScipitie@lemmy.dbzer0.comlinkfedilinkarrow-up1·3 days agoI miss framed this: the concern here for me is not a malicious attack but that you’re still affected in terms of routing: your service becoming unavailable because your hoster or their ISP relied on cloudflare.
Although that should only be possible if the user has a hijacked client or you’re not using HTTPS. Or am I forgetting something?
Cloud flare issue certificates on your behalf when they cache. They also have nameservers. However, I assume that is only for their customers.
I miss framed this: the concern here for me is not a malicious attack but that you’re still affected in terms of routing: your service becoming unavailable because your hoster or their ISP relied on cloudflare.