nextjs - 💡(How to fix) Fix Docs: Applying content security policy with middleware breaks if Chrome preloads page [2 comments, 2 participants]

TL;DR

• Update the matcher in the documentation to correctly handle Chrome's page preloading.

Guidance

• Review the next-router-prefetch and purpose header configurations to ensure they are correctly set for preloaded pages.
• Verify that the Content Security Policy (CSP) is being applied as expected when pages are preloaded by Chrome.
• Check the Next.js documentation on Content Security Policy for any updates or recommendations on handling preloaded pages.
• Consider testing the middleware with different preload scenarios to identify any potential issues.

Example

No code snippet is provided as the issue does not contain sufficient code context.

Notes

• The solution may depend on the specific version of Next.js being used, as well as any custom configurations or middleware implementations.
• Further investigation into the next-router-prefetch and purpose headers may be necessary to determine the root cause of the issue.

Recommendation

• Apply workaround: Update the matcher configuration to handle preloaded pages correctly, as the current documentation may be outdated or incorrect.