-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Don't add nonce to script-src when it already contains 'unsafe-inline' #128
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Closing and reopening so that Travis will hopefully pick this one up. |
TravisCI refuses to run this pull request with an Haven't seen this before. A quick research on Google said that it might be fixed if you login to https://travis-ci.com/ once with your GitHub account. You could restart TravisCI by closing and reopening this pull request afterwards. Could you please try it? |
I managed to clear up the issue with travis support, and it seems they unblocked my email. 🎉 |
@joukevandermaas Thanks a lot for the fix. Not sure if we should backport it to |
Just noticed this bug has been hitting me for a few months, is it safe to update to v2? or can we have a backport please? Thank you very much in advance! |
Sorry for not replying back earlier. Upgrading to v2 should be safe. I think it's more stable than v1 at this point of time even though still considered a pre-release. |
Fixes #127.
I added a test for both the positive (should add nonce) and negative (should not add nonce) case, because I could not find a test for the former and I wanted to make sure I didn't accidentally break that scenario.