-
Notifications
You must be signed in to change notification settings - Fork 169
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
All: add Content-Security-Policy-Report-Only header to all wordpress sites #463
Conversation
4ce4448
to
c16a9ff
Compare
<!doctype html> | ||
<html class="no-js" <?php language_attributes(); ?>> | ||
<head> | ||
<meta charset="utf-8"> | ||
<meta http-equiv="X-UA-Compatible" content="IE=edge"> | ||
|
||
<title><?php | ||
global $page, $paged; |
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.
This was a carryover from the default Wordpress header.php, but these variables are not used.
@timmywil Should we limit this to a STAGING conditional at first? The headers hook function could return early when not. |
@Krinkle Absolutely. I also didn't mean to set csp instead of the report header. Both are fixed now. |
Ref jquery/infrastructure-puppet#54
Ref jquery/infrastructure-puppet#57
This adds a filter that the API sites can override to allow for inline scripts and styles only in API demos.
I'm thinking we can use this in combination with a header set in infrastructure-puppet for non-wordpress sites.