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

Add http-equiv=Content-Security-Policy #88

Closed
sideshowbarker opened this issue Sep 2, 2015 · 3 comments
Closed

Add http-equiv=Content-Security-Policy #88

sideshowbarker opened this issue Sep 2, 2015 · 3 comments
Assignees
@mikewest
Labels
addition/proposal New features or enhancements

Comments

@sideshowbarker
Copy link
Contributor

around http://krijnhoetmer.nl/irc-logs/whatwg/20150902#l-711
@domenic
Copy link
Member

domenic commented Sep 2, 2015

Or .htaccess right?

@sideshowbarker
Copy link
Contributor Author

This bug is just about adding a change to the spec itself, in https://html.spec.whatwg.org/multipage/semantics.html#pragma-directives, as an additional standard value for the http-equiv attribute, and from a patch that @mikewest says he has in his working directory waiting to be finished and committed (tomorrow).

@domenic domenic added the addition/proposal New features or enhancements label Sep 2, 2015
@domenic domenic assigned domenic and unassigned domenic Sep 2, 2015
@mikewest
Copy link
Member

mikewest commented Sep 2, 2015

It's just copy/pasting https://w3c.github.io/webappsec/specs/content-security-policy/#delivery-html-meta-element. Should be straightforward to do tomorrow.

@annevk annevk closed this as completed in 5064a62 Sep 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikewest mikewest

Labels
addition/proposal New features or enhancements
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mikewest @sideshowbarker @domenic