Page 1 of 1

content-security-policy: unsafe-eval

Posted: Wed Jun 17, 2020 3:47 am
by ysantosa
It seems unsafe-eval is needed for CPS (Content-Security-Policy) for the library to be used.

Is this the case ? Is there a way not to require 'unsafe-eval' ?

Particularly in environment where developers may not have the ability / privileges to alter the Response Header of the server serving the library.

Thanks !

Re: content-security-policy: unsafe-eval

Posted: Thu Jun 18, 2020 8:30 am
by Lech Kulikowski
Hello,

Could you explain your issue in more details?

Thank you.