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

wants to merge 1 commit into


None yet

3 participants


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

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

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