Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content Security Policy: The page's settings blocked the loading of a resource at inline ("script-src"). #48461

Closed
1 task done
Southclaws opened this issue Apr 16, 2023 · 3 comments
Labels
bug Issue was opened via the bug report template.

Comments

@Southclaws
Copy link

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Wed Aug 10 14:28:35 PDT 2022; root:xnu-8020.141.5~2/RELEASE_ARM64_T8101
    Binaries:
      Node: 16.13.1
      npm: 8.1.2
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant packages:
      next: 13.3.1-canary.8
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue

Southclaws/storyden#13

To Reproduce

It seems that just setting up an app with the new app directory causes this. There's no clear resolution in any of the error messages.

Describe the Bug

"Content Security Policy: The page's settings blocked the loading of a resource at inline ("script-src")."

And no content will load

image

Expected Behavior

I was expecting the upgrade to not do anything that affected or required changes to my site's CSP.

Which browser are you using? (if relevant)

Firefox latest

How are you deploying your application? (if relevant)

Vercel

@Southclaws Southclaws added the bug Issue was opened via the bug report template. label Apr 16, 2023
@juinquok
Copy link

Seems to be the same bug as #43743

Getting this error on my App as well

@Southclaws
Copy link
Author

This appears to be solved on the latest (13.4.4)

@github-actions
Copy link
Contributor

github-actions bot commented Jul 5, 2023

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 5, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

3 participants
@Southclaws @juinquok and others