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

Don't add nonce to script-src when it already contains 'unsafe-inline' #128

Merged
merged 1 commit into from
Jan 29, 2020

Conversation

joukevandermaas
Copy link
Contributor

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.

Copy link
Collaborator

@jelhan jelhan left a 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.

@jelhan jelhan closed this Jan 27, 2020
@jelhan
Copy link
Collaborator

jelhan commented Jan 27, 2020

Closing and reopening so that Travis will hopefully pick this one up.

@jelhan jelhan reopened this Jan 27, 2020
@jelhan
Copy link
Collaborator

jelhan commented Jan 27, 2020

TravisCI refuses to run this pull request with an Abuse detected error:

abuse-travis

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?

@joukevandermaas
Copy link
Contributor Author

I logged in and now I see this notification:

image

I wonder what I did to them 😄 I will contact their support.

@joukevandermaas
Copy link
Contributor Author

I managed to clear up the issue with travis support, and it seems they unblocked my email. 🎉

@jelhan jelhan merged commit 66e17ad into adopted-ember-addons:master Jan 29, 2020
@jelhan
Copy link
Collaborator

jelhan commented Jan 29, 2020

@joukevandermaas Thanks a lot for the fix. Not sure if we should backport it to v1. If not we should at least make sure to have a first release candidate of v2 soon. @rwjblue any preference? v2 is ready for first release candidate from my side. Just need to get the two pending pull requests merged before.

@urbany
Copy link

urbany commented Jun 22, 2021

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!

@jelhan
Copy link
Collaborator

jelhan commented Aug 2, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Problem with using 'unsafe-inline' in script-src
3 participants