Skip to main content

Utilities for maintaining forwards compatibility with Django releases.

Project description

https://img.shields.io/pypi/pyversions/django-birdcage.svg https://img.shields.io/pypi/v/django-birdcage.svg https://img.shields.io/pypi/status/django-birdcage.svg https://img.shields.io/pypi/l/django-birdcage.svg https://travis-ci.org/freakboy3742/django-birdcage.svg?branch=master

When deploying large websites, operations teams will sometimes deploy new code across a subset of the entire collection of webservers. This approach is called a “Canary” deployment. Most users will continue to be served using the old code; only those users hitting a “Canary” machine will see the new code.

Large websites will often use a Canary when the perceived risk of an upgrade is high. For example, upgrading the Django version from 1.8 LTS to 1.11 LTS on a complex site will generally be considered a risky upgrade; a Canary will be used to test that the upgrade is working as expected before switching all webservers over to the upgraded codebase.

Unfortunately, while Django has good backwards compatibility guarantees, Canary deployments require forwards compatibility as well. This is beacuse a user may have one request served on the new codebase, but subsequent updates served from the old codebase. If information (such as security tokens) aren’t both backwards and forwards compatible between releases, some users will see errors as the move back and forth between old and new codebases.

Birdcage is a project consisting of tools to help you manage Canary upgrades, by provided forwards compatible shims for known problems in Django.

What does Birdcage address?

Django 1.10: Salted CSRF tokens

Django 1.10 introduced a change to CSRF handling to protect against BREACH attacks. Django 1.10+ can interpret Django < 1.10 CSRF tokens; however, if a user is issued a Django 1.10+ CSRF token, it will be rejected as invalid by Django 1.8.

To address this problem, Birdcage provides a version of Django 1.8’s CsrfViewMiddleware that can interpret Django 1.10’s CSRF tokens.

  • In the settings for your Django 1.8 codebase, replace django.middleware.csrf.CsrfViewMiddleware in your MIDDLEWARE setting with birdcage.v1_11.csrf.CsrfViewMiddleware.

  • In your Django 1.10+ codebase, continue to use the Django CsrfViewMiddleware.

Why is it called Birdcage?

Well you have to put your canaries somewhere to keep them safe… :-)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-birdcage-1.0.0.tar.gz (10.2 kB view details)

Uploaded Source

Built Distribution

django_birdcage-1.0.0-py2.py3-none-any.whl (11.8 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file django-birdcage-1.0.0.tar.gz.

File metadata

File hashes

Hashes for django-birdcage-1.0.0.tar.gz
Algorithm Hash digest
SHA256 b0c60fae6092f99134b7e66f1ce4619ff3ffa74a79baf5b59f6ab54fc92f7dec
MD5 b5ebf1dc24ebf6f551f2896d3c2199ca
BLAKE2b-256 3ca87d7c806cadd112fdaffb9ca046278d2a0694c7d41396c8e182598ff6403f

See more details on using hashes here.

File details

Details for the file django_birdcage-1.0.0-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for django_birdcage-1.0.0-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 a8352df78df0c58d8ee9ce453abb02e18cfc630045fb6fe8b16fa436aeab94c7
MD5 d5deb68a5d2375320cc2c705d7ed5646
BLAKE2b-256 11e1449eafcb72ca77c8b671beead1fbd904a7cc616ed6d094dcb7b8beed8314

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page