Closed fraser-langton-student closed 4 years ago
closed by commit a15afbd, in essence because the front end javascript uses inline scripting (i.e. onClick={() => {do_something();}}) we were blocking our own scripts from rendering. I have resolved it by removing the content-security policy that disables inline scripting however this exposes the site XSS attacks. Could fix in the future by removing our inline scripts then re-enabling script-src 'self' in the csp meta tag in index.
Build is rendering a blank page on master, chrome console says:
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-PK0+oytTbAxJr7VkjNUTdksxXhVyVzLKR6UrHreRNAA='), or a nonce ('nonce-...') is required to enable inline execution.
@NDoolan360 @fwongkwok @calvinsagar