Gwildor commented on issue #36268: URL: https://github.com/apache/superset/issues/36268#issuecomment-3580439343
I've managed to solve this on my end. The solution had nothing to do with `img-src`, and luckily also nothing to do with different Talisman configurations. The problem was with `connect-src`. Apparently, for PDFs a browser (or maybe only a headless browser) retrieves the content through connect-src instead of img-src. I will close this, but I do have some considerations to close with: * Should Superset throw an error if generating the PDF failed? Now it just does nothing, leaving the user confused. * Should this behaviour (requirement for connect-src) be documented? I couldn't find anything in the docs about this. * Should the connect-src in `superset/config.py` match the img-src? I see there are some CDNs listed in the img-src which are missing in the connect-src. I don't know if those are important and if this could cause other issues. -- 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]
