3 ms·
It feels like they didn't learn the root lesson - move your 200MB setup file to a subdomain. You shouldn't host large assets like this on the same domain as yo
by dugmartin 3y ago
It feels like they didn't learn the root lesson - move your 200MB setup file to a subdomain. You shouldn't host large assets like this on the same domain as your marketing/app site even if there is a CDN fronting it because an attacker can simply add a random query string to bust through the CDN cache and cause the cache miss to hit your box. The subdomain should be hosted on a different box and fronted possibly with a different CDN provider so that any large scale attack doesn't affect your marketing/app site (either due to your CDN provider or upstream network provider temporarily black holing you).
- viraptor 3y ago> an attacker can simply add a random query string to bust through the CDN cache You can configure the cache so that they can't do it: https://developers.cloudflare.com/cache/troubleshooting/cache-everything-ignore-query-strings/ https://developers.cloudflare.com/cache/troubleshooting/cach... Without knowing their specific configuration, we don't have enough info to complain about that. Also the separate domain doesn't really change much with CF in front. It could be nice for a few reasons, but it's not really bad. If you have a reasonable CDN already, there's really not much point getting a different one.