Skip to content

Releases: brokenhandsio/VaporSecurityHeaders

1.1.0

21 Sep 17:42
Compare
Choose a tag to compare

Vapor Security Headers 1.1.0

PR #8 - Add Swift 4 support to the library

1.0.0

18 May 15:24
Compare
Choose a tag to compare

Vapor Security Headers 1.0.0

This is the first major release of Vapor Security Headers, updated for Vapor 2 and ready to use. Take a look at the README for latest instructions on how to use.

0.4.0 Beta 3

03 May 19:11
Compare
Choose a tag to compare
0.4.0 Beta 3 Pre-release
Pre-release

Updates to latest Vapor 2 changes

0.4.0 Beta 2

22 Apr 00:12
Compare
Choose a tag to compare
0.4.0 Beta 2 Pre-release
Pre-release

Vapor Security Headers 0.4.0 Beta 2

This release updates Vapor Security Headers to work with the latest Vapor 2 changes and as a result there are some major breaking changes.

Breaking Changes

  • XssProtectionConfiguration is now XSSProtectionConfiguration
  • The SecurityHeaders initialiser is now internal and you should move over to using the new SecurityHeadersFactory. This will make it easier to build up your security headers and add it to your Droplet with the new Vapor 2 changes. See the README for details

New Usage

For how to use the library with Vapor 2, see the README

0.4.0-beta.1

13 Apr 12:28
Compare
Choose a tag to compare
0.4.0-beta.1 Pre-release
Pre-release

Vapor Security Headers 0.4.0-beta.1

This release adds support for Vapor 2. There are no other changes

0.3.0

31 Mar 07:48
Compare
Choose a tag to compare

Vapor Security Headers 0.3.0

The release adds the ability to set page specific Content Security Policies to allow you to enable different content only when needed rather than on a whole site basis.

To add a specific CSP to a request, create a separate ContentSecurityPolicyConfiguration and then add it to the request. For example, inside a route handler, you could do:

let pageSpecificCSPVaue = "default-src 'none'; script-src https://comments.disqus.com;"
let pageSpecificCSP = ContentSecurityPolicyConfiguration(value: pageSpecificCSPValue)
request.contentSecurityPolicy = pageSpecificCSP

0.2.1

30 Mar 21:16
Compare
Choose a tag to compare

Vapor Security Headers 0.2.1

This release adds the ability to set a referrer policy on the API Security Headers. The use case for this is for those use the API headers for a server that is using a React front-end with a single page.

The referrer policy can be set with:

let referrerConfig = ReferrerPolicyConfiguration(.strictOrigin)
let securityHeaders = SecurityHeaders.api(referrerPolicyConfiguration: referrerConfig)

0.2.0

23 Feb 22:22
Compare
Choose a tag to compare

Vapor Security Headers 0.2.0

This release adds support for the Referrer Policy header which basically dictates when then Referrer header can be sent with requests. The W3C proposal can be found here and a good explanation of the header can be found on Scott Helme's Blog.

There are no breaking with this release. To set this new header, just create a configuration and pass it to the security headers setup:

let referrerConfig = ReferrerPolicyConfiguration(.sameOrigin)
let securityHeaders = SecurityHeaders(referrerPolicyConfiguration: referrerConfig)

0.1.1

17 Feb 08:17
Compare
Choose a tag to compare

VaporSecurityHeaders 0.1.1

Fixes:

  • Not being able to use the library due to access issues...you know actually making it usable!

0.1.0

16 Feb 13:00
Compare
Choose a tag to compare

Vapor Security Headers 0.1.0

This is the initial release of the Vapor Security Headers. Please see the README for information on how to use.