Skip to content

Commit bac6dae

Browse files
authored
Upgrade version and docs to 7.0 (#528)
## All PRs: * [x] Has tests * [x] Documentation updated ## Adding a new header N/A ## Adding a new CSP directive N/A Closes #480
1 parent 6b5eb33 commit bac6dae

File tree

3 files changed

+14
-2
lines changed

3 files changed

+14
-2
lines changed

docs/upgrading-to-7-0.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
## X-Xss-Protection is set to 0 by default
2+
3+
Version 6 and below of `secure_headers` set the `X-Xss-Protection` to `1; mode=block` by default. This was done to protect against reflected XSS attacks. However, this header is no longer recommended (see https://github.com/github/secure_headers/issues/439 for more information).
4+
5+
If any functionality in your app depended on this header being set to the previous value, you will need to set it explicitly in your configuration.
6+
7+
```ruby
8+
# config/initializers/secure_headers.rb
9+
SecureHeaders::Configuration.default do |config|
10+
config.x_xss_protection = "1; mode=block"
11+
end
12+
```

lib/secure_headers/version.rb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# frozen_string_literal: true
22

33
module SecureHeaders
4-
VERSION = "6.5.0"
4+
VERSION = "7.0.0"
55
end

secure_headers.gemspec

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Gem::Specification.new do |gem|
1313
gem.description = 'Add easily configured security headers to responses
1414
including content-security-policy, x-frame-options,
1515
strict-transport-security, etc.'
16-
gem.homepage = "https://github.com/twitter/secureheaders"
16+
gem.homepage = "https://github.com/github/secure_headers"
1717
gem.license = "MIT"
1818
gem.files = `git ls-files`.split($INPUT_RECORD_SEPARATOR)
1919
gem.executables = gem.files.grep(%r{^bin/}).map { |f| File.basename(f) }

0 commit comments

Comments
 (0)