Replies: 1 comment 2 replies
-
Your server is responsible for specifying its content policies when it serves your app. You will need to set the appropriate headers (as you have done). This is not a bug or anything, just a detail of how browsers work. Now that you have no errors loading your assets, see if the table is present but 0 height or width. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying to load the perspective table in angular app with the sample url https://xxx/yy. The perspective worker is creating in the base url http://xxx and throwing the content security policy issues.
Is this a problem with creating the worker in the base path? If so, how can we override the worker creation in a specified path, say https://xxx/yy.
Also tried to set the custom request header like this. "script-src 'self' https://unpkg.com/@finos/perspective-viewer-datagrid 'unsafe-eval' 'unsafe-inline'; object-src 'self'; worker-src 'self' https://unpkg.com/@finos/perspective-viewer-datagrid blob:;" Then the error disappeared but still the table is not loading. Is there any work around for this issue?
Beta Was this translation helpful? Give feedback.
All reactions