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
- CSP: Add support for trusted-types, require-trusted-types-for directive (@JackMc): https://github.com/github/secure_headers/pull/486
8
+
9
+
## 6.3.4
10
+
11
+
- CSP: Do not deduplicate alternate schema source expressions (@keithamus): https://github.com/github/secure_headers/pull/478
12
+
1
13
## 6.3.3
2
14
3
15
Fix hash generation for indented helper methods (@rahearn)
@@ -58,7 +70,7 @@ NOTE: this version is a breaking change due to the removal of HPKP. Remove the H
58
70
59
71
## 5.0.0
60
72
61
-
Well this is a little embarassing. 4.0 was supposed to set the secure/httponly/samesite=lax attributes on cookies by default but it didn't. Now it does. - See the [upgrading to 5.0](docs/upgrading-to-5-0.md) guide.
73
+
Well this is a little embarrassing. 4.0 was supposed to set the secure/httponly/samesite=lax attributes on cookies by default but it didn't. Now it does. - See the [upgrading to 5.0](docs/upgrading-to-5-0.md) guide.
62
74
63
75
## 4.0.1
64
76
@@ -182,7 +194,7 @@ end
182
194
183
195
## 3.4.0 the frame-src/child-src transition for Firefox.
184
196
185
-
Handle the `child-src`/`frame-src` transition semi-intelligently across versions. I think the code best descibes the behavior here:
197
+
Handle the `child-src`/`frame-src` transition semi-intelligently across versions. I think the code best describes the behavior here:
**main branch represents 6.x line**. See the [upgrading to 4.x doc](docs/upgrading-to-4-0.md), [upgrading to 5.x doc](docs/upgrading-to-5-0.md), or [upgrading to 6.x doc](docs/upgrading-to-6-0.md) for instructions on how to upgrade. Bug fixes should go in the 5.x branch for now.
3
+
**main branch represents 7.x line**. See the [upgrading to 4.x doc](docs/upgrading-to-4-0.md), [upgrading to 5.x doc](docs/upgrading-to-5-0.md), [upgrading to 6.x doc](docs/upgrading-to-6-0.md)or [upgrading to 7.x doc](docs/upgrading-to-7-0.md)for instructions on how to upgrade. Bug fixes should go in the `6.x` branch for now.
4
4
5
5
The gem will automatically apply several headers that are related to security. This includes:
6
6
- Content Security Policy (CSP) - Helps detect/prevent XSS, mixed-content, and other classes of attack. [CSP 2 Specification](https://www.w3.org/TR/CSP2/)
@@ -11,11 +11,11 @@ The gem will automatically apply several headers that are related to security.
11
11
- X-Frame-Options (XFO) - Prevents your content from being framed and potentially clickjacked. [X-Frame-Options Specification](https://tools.ietf.org/html/rfc7034)
12
12
- X-XSS-Protection - [Cross site scripting heuristic filter for IE/Chrome](https://msdn.microsoft.com/en-us/library/dd565647\(v=vs.85\).aspx)
13
13
- X-Content-Type-Options - [Prevent content type sniffing](https://msdn.microsoft.com/library/gg622941\(v=vs.85\).aspx)
-Expect-CT - Only use certificates that are present in the certificate transparency logs. [Expect-CT draft specification](https://datatracker.ietf.org/doc/draft-stark-expect-ct/).
18
-
-Clear-Site-Data - Clearing browser data for origin. [Clear-Site-Data specification](https://w3c.github.io/webappsec-clear-site-data/).
-expect-ct - Only use certificates that are present in the certificate transparency logs. [expect-ct draft specification](https://datatracker.ietf.org/doc/draft-stark-expect-ct/).
18
+
-clear-site-data - Clearing browser data for origin. [clear-site-data specification](https://w3c.github.io/webappsec-clear-site-data/).
19
19
20
20
It can also mark all http cookies with the Secure, HttpOnly and SameSite attributes. This is on default but can be turned off by using `config.cookies = SecureHeaders::OPT_OUT`.
21
21
@@ -62,7 +62,6 @@ SecureHeaders::Configuration.default do |config|
62
62
# directive values: these values will directly translate into source directives
63
63
default_src:%w('none'),
64
64
base_uri:%w('self'),
65
-
block_all_mixed_content:true, # see https://www.w3.org/TR/mixed-content/
66
65
child_src:%w('self'), # if child-src isn't supported, the value for frame-src will be set.
67
66
connect_src:%w(wss:),
68
67
font_src:%w('self' data:),
@@ -92,18 +91,21 @@ SecureHeaders::Configuration.default do |config|
92
91
end
93
92
```
94
93
94
+
### Deprecated Configuration Values
95
+
*`block_all_mixed_content` - this value is deprecated in favor of `upgrade_insecure_requests`. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/block-all-mixed-content for more information.
96
+
95
97
## Default values
96
98
97
99
All headers except for PublicKeyPins and ClearSiteData have a default value. The default set of headers is:
0 commit comments