hard20 pts · first answer countscspweb-securitynextjs

Nonce-based CSP trade-off

You add a strict Content Security Policy with a fresh nonce on every request in a Next.js app. What is the main trade-off?

A.Pages that use the nonce must be rendered per request, so they lose static generation and CDN cachingB.Nonces can safely be reused across many requests, so the cached HTML and CDN caching are not affected at allC.Nonces only apply to CSS, so scripts stay unprotectedD.The site can no longer be served over HTTPS

Discussion 0

Join free to post in the discussion.

Nonce-based CSP trade-off

Discussion 0

Related questions