Skip to content

This repository contains a middleware which automatically sets SameSite attribute for session and csrf cookies in legacy versions of Django.

License

Notifications You must be signed in to change notification settings

gilgtc/django-cookies-samesite

 
 

Repository files navigation

django-cookies-samesite

https://travis-ci.org/jotes/django-cookies-samesite.svg?branch=master

Repository status

The project isn't actively maintained anymore. If you want to help and add a link to your fork, add it there: jotes#50 .

Description

This repository contains a middleware which automatically sets SameSite attribute for session and csrf cookies in legacy versions of Django e.g. 1.11.x, 2.2.x or 3.0.x.

This module is not needed for Django 3.1.x which introduces full support of SameSite flag for session and csrf cookie.

Quickstart

Install django-cookies-samesite:

pip install django-cookies-samesite

Add the middleware to the top of MIDDLEWARE_CLASSES:

MIDDLEWARE_CLASSES = (
    'django_cookies_samesite.middleware.CookiesSameSite',
    ...
)

Important

If you're planning to use this middleware together with the newer version of Django (>3.0.x), and you want to e.g. set the SameSite attribute to none, then you have to add DCS_ prefix to all django-cookies-samesite settings (see examples below).

It will help you to avoid bugs caused by the conflicting settings names.

Related bug: jotes#19

Set your preferred SameSite policy in settings.py:

SESSION_COOKIE_SAMESITE = 'lax'
# or
DCS_SESSION_COOKIE_SAMESITE = 'Lax'

This can be 'Lax', 'None', 'Strict', or None to disable the flag. Also, you can set this flag in your custom cookies:

SESSION_COOKIE_SAMESITE_KEYS = {'my-custom-cookies'}
# or
DCS_SESSION_COOKIE_SAMESITE_KEYS = {'my-custom-cookies'}

After that you should be able to see the SameSite flag set for session and csrf cookies.

You can set the SameSite flag on all cookies (even on those coming from third-party Django apps):

SESSION_COOKIE_SAMESITE_FORCE_ALL = True
# or
DCS_SESSION_COOKIE_SAMESITE_FORCE_ALL = True

The sessionid and csrftoken cookies are automatically handled by the middleware. This behavior can be disabled with:

SESSION_COOKIE_SAMESITE_FORCE_CORE = False
# or
DCS_SESSION_COOKIE_SAMESITE_FORCE_CORE = False

Running Tests

Does the code actually work?

source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install tox
(myenv) $ tox

Credits

Tools used in rendering this package:

Contributors

About

This repository contains a middleware which automatically sets SameSite attribute for session and csrf cookies in legacy versions of Django.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 90.5%
  • HTML 5.4%
  • Makefile 4.1%