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.

Sign up for GitHub

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

Jump to bottom

Content Security Policy #10

Open
Phhere opened this issue Jun 13, 2013 · 1 comment
Open

Content Security Policy #10

Phhere opened this issue Jun 13, 2013 · 1 comment
Labels
new Feature

Comments

@Phhere
Copy link
Contributor

Phhere commented Jun 13, 2013

We should support the Content Security Policy so XSS issues are nearly impossible. This means that there can't be any inline < script >-Tags or eval() in JS and there will be no onclick / onchange /... attributes.
@derchrisuk
Copy link
Member

https://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
new Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@derchrisuk @Phhere