Useful information in the reports module : xclass, ajax, cliKeys, eID, general status of the system (encoding, DB, php vars...), hooks, compare local and TER extension (diff), used content type, used plugins, ExtDirect... It can really help you during migration or new existing project (to have a global reports of the system).
Other
12
stars
11
forks
source link
[BUG] Content Security Policy in 'plugins content type' #43
I'm getting this error when selecting 'plugins content type' with activated 'Security: backend enforce content security policy':
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'nonce-WI_zioRv4UnzdcueKlie2mZ6tmx46LqnwQ9ANaICSW9kTCpce9iBaQ' 'report-sample'". Either the 'unsafe-inline' keyword, a hash ('sha256-hR9evmmtfYpk8OMZk2os+R4KO344Hmnek+AWnmYlWFc='), or a nonce ('nonce-...') is required to enable inline execution.
Apen
commented
7 months ago
I'm getting this error when selecting 'plugins content type' with activated 'Security: backend enforce content security policy':
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'nonce-WI_zioRv4UnzdcueKlie2mZ6tmx46LqnwQ9ANaICSW9kTCpce9iBaQ' 'report-sample'". Either the 'unsafe-inline' keyword, a hash ('sha256-hR9evmmtfYpk8OMZk2os+R4KO344Hmnek+AWnmYlWFc='), or a nonce ('nonce-...') is required to enable inline execution.