讨论： 为第三方脚本和样式表使用子资源完整性校验

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

暂无译文，显示原文。 原文

The article presents pinning a CDN URL as the goal and self-hosting as the fallback for content that varies, and I would reverse the order. With browsers partitioning the HTTP cache by site, a public CDN no longer saves a fetch; what remains is a third-party dependency for availability (a CDN outage or a blocked domain takes the page's script with it), a leak of every visitor's address and referrer to the CDN operator, and an extra connection on first load. A copy in your own build pipeline, served from your origin, gets exactly the integrity guarantee SRI provides, because the build produced the bytes and the deploy cannot change them without changing the page that references them, and it needs neither `crossorigin` nor CORS headers on anyone else's server. SRI on a third-party URL is then the right tool for the case where you cannot self-host: a vendor that licenses its script for loading from its host only, or a tag you must load from a fixed URL. The 'watch your error tracker' bullet also becomes simpler, because a self-hosted file cannot change under you; the remaining reason to watch is your own deploy.

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

暂无译文，显示原文。 原文

Two facts that bear on the 'CDN plus hash' pattern. The shared-cache argument for public CDNs is gone: Chrome partitions the HTTP cache by top-level site since version 86 (2020), Firefox since 85 (2021), and Safari earlier, so a copy of `lib@1.2.3` fetched on another site is never reused on yours; a third-party CDN now costs a DNS lookup, a connection and a privacy leak with no cache benefit. And the Pitfalls' 'resources that legitimately vary per request cannot be pinned' has a documented case: the polyfill.io service, which served different code per user agent and therefore could not carry an integrity hash, was sold in early 2024 and by June 2024 was reported to serve malicious code to visitors of the sites that still embedded it. One mechanical detail: module scripts (`type=module`) are always fetched in CORS mode, so for them the `crossorigin` attribute only chooses whether credentials are sent, and the integrity check works cross-origin as long as the server sends the CORS header.