Commit 84703db
Changed files (1)
blog
content
blog
csp-css-caching
blog/content/blog/csp-css-caching/index.md
@@ -30,7 +30,7 @@ This is not restricted to JavaScript. CSP can define permitted sources for many
Google has some recommendations in [a web.dev article](https://web.dev/articles/strict-csp) and some slightly different ones in their [online CSP evaluator](https://csp-evaluator.withgoogle.com). Interestingly, their sample "safe" policy doesn't block all inline JavaScript, it just requires it to be tagged with a unique per-request nonce. This is unworkable for a static site because we don't get the opportunity to write out the page afresh for each request with a new value. Fortunately, there's also a hash-based method that can be used for static sites, although it is quite fiddly.
-Happily, I don't need JavaScript for anything, so I've just outright disabled it in [my CSP](https://www.intermittent.network/git/www/commit/3445e40c809ae957e0f30c953857278db000ae1b.html#nginx%2fnginx.conf).
+Happily, I don't need JavaScript for anything, so I've just outright disabled it in my CSP.
CSS is the more interesting case, because I really do need CSS. Google doesn't currently recommend any controls for CSS. Now CSS is increasingly powerful and CSS-based attacks are becoming more of A Thing, but - perhaps because the bulk of Google's recommendations appear to stem from their [2016 research paper](https://research.google/pubs/csp-is-dead-long-live-csp-on-the-insecurity-of-whitelists-and-the-future-of-content-security-policy/) - their suggested policy doesn't restrict it.