refactor: update Content Security Policy to allow 'wasm-unsafe-eval' and set nonce in response headers

This commit is contained in:
CodingOnStar 2025-10-20 12:23:41 +08:00
parent faefc3492e
commit 1f4c541c0d

View File

@ -56,7 +56,7 @@ export function middleware(request: NextRequest) {
contentSecurityPolicyHeaderValue, contentSecurityPolicyHeaderValue,
) )
response.headers.set('x-nonce', nonce) // response.headers.set('x-nonce', nonce)
response.headers.set( response.headers.set(
'Content-Security-Policy', 'Content-Security-Policy',
contentSecurityPolicyHeaderValue, contentSecurityPolicyHeaderValue,