varun-verma-code commented on issue #30761:
URL: https://github.com/apache/superset/issues/30761#issuecomment-2722994068

   https://github.com/apache/superset/issues/30761#issuecomment-2464357595
   @ruslan-murzag I have added the config to both places, however, I still see 
the same issue. Here's my config:
   `TALISMAN_CONFIG = {
       "content_security_policy": {
           "default-src": ["'self'"],
           "img-src": ["'self'", "data:","blob:"],
           "worker-src": ["'self'", "blob:"],
           "connect-src": [
               "'self'",
               "https://api.mapbox.com";,
               "https://events.mapbox.com";,
           ],
           "object-src": "'none'",
           "style-src": ["'self'", "'unsafe-inline'"],
           "script-src": ["'self'", "'strict-dynamic'"],
       },
       "content_security_policy_nonce_in": ["script-src"],
       "force_https": False,
   }
   # React requires `eval` to work correctly in dev mode
   TALISMAN_DEV_CONFIG = {
       "content_security_policy": {
           "default-src": ["'self'"],
           "img-src": ["'self'", "data:","blob:"],
           "worker-src": ["'self'", "blob:"],
           "connect-src": [
               "'self'",
               "https://api.mapbox.com";,
               "https://events.mapbox.com";,
           ],
           "object-src": "'none'",
           "style-src": ["'self'", "'unsafe-inline'"],
           "script-src": ["'self'", "'unsafe-inline'", "'unsafe-eval'"],
       },
       "content_security_policy_nonce_in": ["script-src"],
       "force_https": False,
   }`
   
   Am I missing anything?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to