id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
17083	sessions.backends.cache does not allow non-default cache to be configured	charles@…	Aymeric Augustin	"Django 1.3 introduced support for more than one cache to be defined. However, the cache-based session store backend does not support using a non-default backend.

A configuration option should be available to select the cache to be used by the Django session store cache backend.

Use case: One may want the session store to be kept in a replicated cache (to prevent user-visible disruption during failover events) vs cached data which can be regenerated without user-visible impact beyond performance.

Use case: One may want the session store to be kept in a distributed cache while keeping other content in a system-local cache."	New feature	closed	contrib.sessions	dev	Normal	fixed			Ready for checkin	1	0	0	0	0	0