-
Notifications
You must be signed in to change notification settings - Fork 3
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
Fix martor editors not working because of content security policy #284
Comments
fblampe
changed the title
Fix martor editors not working
Fix martor editors not working because of content security policy
Aug 28, 2023
fblampe
added a commit
that referenced
this issue
Aug 28, 2023
fblampe
added a commit
that referenced
this issue
Aug 28, 2023
[#284] Workaround: Remove content security policy for now
As a workaround, I removed the problematic line for now so we can keep deploying without breaking anything. |
cafischer
added a commit
that referenced
this issue
Sep 6, 2023
mdrie
added a commit
that referenced
this issue
Sep 7, 2023
[#284] add content security header that works with martor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Editors just look like this and cannot be used:
The reason are content security policy errors that show up in the browser console:
They are caused by the updated nginx config: https://github.com/GermanZero-de/klimaschutzmonitor/pull/275/files#diff-1566418be847e3065680f7aa0ef6b85f31cee192217d17d0cce702e4ab916433R11
Looks like we might need some exceptions for martor..? @cafischer could you have a look at this since you probaly already looked into CSP stuff recently?
The text was updated successfully, but these errors were encountered: