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

Drop use of 'new window.Function' to satisfy Content-Security-Policy #1501

Open
dracos opened this issue Aug 16, 2016 · 0 comments
Open

Drop use of 'new window.Function' to satisfy Content-Security-Policy #1501

dracos opened this issue Aug 16, 2016 · 0 comments

Comments

@dracos
Copy link
Contributor

dracos commented Aug 16, 2016

A Content-Security-Policy header (without unsafe-eval) will block any use of new Function, even one that's empty. I think the offending line at

oRequest._object.onreadystatechange = new window.Function;
can be safely set to null instead.

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

1 participant