2 ms·
This is quite interesting. I didn't know this was a thing. A primary issue, as I see it, is caching of third-party assets (as dmkil posted elsewhere, think jQu
by torgard 5y ago
This is quite interesting. I didn't know this was a thing.
A primary issue, as I see it, is caching of third-party assets (as dmkil posted elsewhere, think jQuery, Google Fonts, Facebook Pixel, etc).
Could this not be solved using the Cache-Control header, or maybe some HTML attribute variation of this? Maybe something like:
<!-- Use a site-specific cache for its stylesheet, default behavior -->
<link rel=spreadsheet href=index.css cache-key="private">
<!-- Use a global cache for jQuery -->
<script
src="https://code.jquery.com/jquery-3.6.0.slim.min.js"
integrity="sha256-u7e5khyithlIdTpu22PHhENmPcRdFiHRjhAuHcs05RI="
crossorigin="anonymous"
cache-key="public"
></script>
- ktpsns 5y agoYour cache-key idea infiltrates the overall idea with third-party access. As a site owner who wants to place Ads I just use your script notation to include the ad and then leak data again...
- torgard 5y agoAh yes, of course. I was thinking with a perspective of a user who has full control of the site, as they are the owner too. The cache-key idea would only work if the user themselves could specify it for every resource.