django-feature-policy 1.0.1

Requirements

Tested with all combinations of:

• Python: 3.6

• Django: 2.0, 2.1

Installation

Install with pip:

pip install django-feature-policy

Then add the middleware, best after Django’s SecurityMiddleware as it does similar addition of security headers that you’ll want on every response:

MIDDLEWARE = [
  ...
  'django.middleware.security.SecurityMiddleware',
  'django_feature_policy.FeaturePolicyMiddleware',
  ...
]

By default no header will be set, configure the setting as below.

Setting

Change the FEATURE_POLICY setting to configure what Feature-Policy header gets set.

This should be a dictionary laid out with:

• Keys as the names of browser features - a full list is available on the MDN article.

• Values as lists of strings, where each string is either an origin, e.g. 'https://example.com', or of the special values 'self', 'none', or '*'. If there is just one value, no containing list is necessary. Note that in the header, special values like 'none' include single quotes around them - do not include these quotes in your Python string, they will be added by the middleware.

If the keys or values are invalid, ImproperlyConfigured will be raised at instantiation time, or when processing a response. The current feature list is pulled from the JavaScript API with document.policy.allowedFeatures() on the latest Chrome build.

FEATURE_POLICY = {
    'geolocation': 'none',
}

FEATURE_POLICY = {
    'autoplay': ['self', 'https://archive.org'],
}

Pending release

1.0.1 (2019-01-02)

• Support for new ‘lazyload’ feature, per https://www.chromestatus.com/feature/5641405942726656.

1.0.0 (2018-10-24)

• First release, supporting adding the header with a middleware.