Fixed #17083 -- Allow cached based sessions to use a custom cache backend #169

Closed
wants to merge 1 commit into
from

Projects

None yet

3 participants

@tomkins

Django currently lacks a way of using a custom cache backend in django.contrib.sessions - it always uses the default backend.

https://code.djangoproject.com/ticket/17083

This commit will default to the "sessions" backend, but will fall back to the "default" backend, this is similar to django.contrib.staticfiles behaviour.

@apollo13
Django member

Can you please add tests which check that the backend in question is actually used?

@aaugustin aaugustin closed this Oct 27, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment