You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -57,13 +57,13 @@ SecureHeaders::Configuration.default do |config|
57
57
plugin_types:%w(application/x-shockwave-flash),
58
58
block_all_mixed_content:true, # see [http://www.w3.org/TR/mixed-content/](http://www.w3.org/TR/mixed-content/)
59
59
upgrade_insecure_requests:true, # see https://www.w3.org/TR/upgrade-insecure-requests/
60
-
report_uri:%w(https://example.com/uri-directive)
60
+
report_uri:%w(https://report-uri.io/example-csp)
61
61
}
62
62
config.hpkp = {
63
63
report_only:false,
64
64
max_age:60.days.to_i,
65
65
include_subdomains:true,
66
-
report_uri:"https://example.com/uri-directive",
66
+
report_uri:"https://report-uri.io/example-hpkp",
67
67
pins: [
68
68
{sha256:"abc"},
69
69
{sha256:"123"}
@@ -175,7 +175,7 @@ When manipulating content security policy, there are a few things to consider. T
175
175
176
176
#### Append to the policy with a directive other than `default_src`
177
177
178
-
The value of `default_src` is joined with the addition. Note the `https:` is carried over from the `default-src` config. If you do not want this, use `override_content_security_policy_directives` instead. To illustrate:
178
+
The value of `default_src` is joined with the addition if the it is a [fetch directive](https://w3c.github.io/webappsec-csp/#directives-fetch). Note the `https:` is carried over from the `default-src` config. If you do not want this, use `override_content_security_policy_directives` instead. To illustrate:
179
179
180
180
```ruby
181
181
::SecureHeaders::Configuration.default do |config|
0 commit comments