You are viewing the documentation for the 2.8.16 release in the 2.8.x series of releases. The latest stable release series is 3.0.x.

§Configuring Security Headers

Play provides a security headers filter that can be used to configure some default headers in the HTTP response to mitigate security issues and provide an extra level of defense for new applications.

§Enabling the security headers filter

Note: As of Play 2.6.x, the Security Headers filter is included in Play’s list of default filters that are applied automatically to projects. See the Filters page for more information.

To enable the security headers filter manually, add the security headers filter to your filters in application.conf:

play.filters.enabled += "play.filters.headers.SecurityHeadersFilter"

§Configuring the security headers

Scaladoc is available in the play.filters.headers package.

The filter will set headers in the HTTP response automatically. The settings can be configured through the following settings in application.conf

Note: The contentSecurityPolicy property has been deprecated and the default value has been set to null in Play 2.7. Please see CspFilter for details.

Any of the headers can be disabled by setting a configuration value of null, for example:

play.filters.headers.frameOptions = null

For a full listing of configuration options, see the Play filters reference.conf.

§Action-specific overrides

Security headers may be overridden in specific actions using withHeaders on the result:

Ok("Index").withHeaders(SecurityHeadersFilter.REFERRER_POLICY -> "my page-specific header")

Any security headers not mentioned in withHeaders will use the usual configured values
(if present) or the defaults. Action-specific security headers are ignored unless
play.filters.headers.allowActionSpecificHeaders is set to true in the configuration.

Next: Configuring CORS