You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main reason to separate CSS from HTML is so that you can reuse the CSS with other pages on the same website. The test HTML is only one page.
The primary remaining reason not to inline it is that allowing inlining of CSS can be a security risk, which a strong Content Security Policy would block. This can be mitigated if you include a hash of your inline stylesheet (sans trailing whitespace?).
The main reason to separate CSS from HTML is so that you can reuse the CSS with other pages on the same website. The test HTML is only one page.
The primary remaining reason not to inline it is that allowing inlining of CSS can be a security risk, which a strong Content Security Policy would block. This can be mitigated if you include a hash of your inline stylesheet (sans trailing whitespace?).
A nonce could also work, but I have no idea how one would implement it in Caddy, and a hash seems more appropriate for static content anyway.
https://content-security-policy.com/hash/ has more info on hashes.
The text was updated successfully, but these errors were encountered: