django-feature-policy 2.3.0

Set the draft security HTTP header Feature-Policy on your Django app.

django-feature-policy

Set the draft security HTTP header Feature-Policy on your Django app.

Requirements

Python 3.5-3.7 supported.

Django 1.11-2.2 supported.

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 W3 Spec repository. The MDN article is also worth reading.

• 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.featurePolicy.allowedFeatures() on Chrome.

Examples

Disable geolocation from running in the current page and any iframe:

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

Allow autoplay from the current origin and iframes from https://archive.org:

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

History

Pending release

2.3.0 (2019-05-19)

• Update Python support to 3.5-3.7, as 3.4 has reached its end of life.

• Make the generated header deterministic by iterating the settings dict in sorted order.

• Support Django 1.11 for completeness.

2.2.0 (2019-05-08)

• Fix interpretation of ‘*’ by not automatically adding quotes.

• Optimize header generation to reduce impact on every request.

2.1.0 (2019-04-28)

• Tested on Django 2.2. No changes were needed for compatibility.

2.0.0 (2019-03-29)

• Updated to the latest set of features from Chrome. ‘animations’, ‘image-compression’, and ‘max-downscaling-image’ have been removed, whilst ‘document-domain’, ‘font-display-late-swap’, ‘layout-animations’, ‘oversized-images’, ‘unoptimized-images’, and ‘wake-lock’ have been added. See more at https://github.com/w3c/webappsec-feature-policy/blob/master/features.md .

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.