I invite everyone (even those not affected in this instance) to consider switching away from relying on random third parties for your hosting. Like wtf how is did this ever become the norm even when there was a slight performance advantage from a shared cache, which doesn't even exist anymore these days.
A very specific problem with third party hosts : if you use noscript and only allow main domain script as a default, you have to either whitelist those CDN or authorize them on every site using it. Not the best experience. Especially with some sites having dozens of third party scripts so instead of trying to find the right one(s) to authorize you just close the tab and forget about it.
I do both. If you are loading a JS lib then check for its existence on the client. If it's not found load the resource from your server. You could also achieve this on the server side.
Why? If you care about being even remotely reliable (hinted at with "production-focused"), why would you do this? Just use the same host as where you serve everything else from.
Browsers have partitioned caches per origin for over 10 years, so there's no performance gains from getting cache hits from other websites.
account42|1 year ago
arkh|1 year ago
alzoid|1 year ago
madeofpalk|1 year ago
Browsers have partitioned caches per origin for over 10 years, so there's no performance gains from getting cache hits from other websites.