Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content Security Policy errors with style-src self #143

Closed
bunsenmcdubbs opened this issue Jul 7, 2016 · 2 comments
Closed

Content Security Policy errors with style-src self #143

bunsenmcdubbs opened this issue Jul 7, 2016 · 2 comments

Comments

@bunsenmcdubbs
Copy link
Contributor

I'm not sure if this is an error or issue with my local configuration but in both Chrome (51) and Firefox (40, 45) I get errors relating to the CSP.

Chrome:

ng-file-upload.js:601 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-QNZepBp2sFHapu/mZlZx9qzx2uVkSgN5NkyJhrAa8XM='), or a nonce ('nonce-...') is required to enable inline execution.

jquery.js:5114 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-1nVQdHiAzq+yQt4PZ8OE7a29XlxBFIzESqqj+rz4Jdc='), or a nonce ('nonce-...') is required to enable inline execution.

Firefox:

Content Security Policy: The page's settings blocked the loading of a resource at self ("style-src http://localhost:8080").

It doesn't seem to break any functionality on the site and its interesting to see that it's frequency is not constant (not always the same number of errors per page load etc). I don't think it's a very high priority but it does come up a lot in the Javascript console.

@syjer
Copy link
Member

syjer commented Jul 7, 2016

@bunsenmcdubbs yes we are aware :). I guess that we will relax the CSP policy for css. Should not be too dangerous.

@syjer
Copy link
Member

syjer commented Jul 28, 2016

fixed :)

We have enabled unsafe-inline for the style.

@syjer syjer closed this as completed Jul 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants