#29203: Cached Session may cause losing a session, when it failed to connect to cache backend -------------------------------------+------------------------------------- Reporter: Kenial Sookyum Lee | Owner: nobody Type: Bug | Status: new Component: contrib.sessions | Version: master Severity: Normal | Resolution: Keywords: session cookie, | Triage Stage: cached session | Unreviewed Has patch: 1 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Kenial Sookyum Lee): When I tested the settings with SESSION_ENGINE = "django.contrib.sessions.backends.cached_db" (ie. 'write-through cache'), I didn't get through this bug. Configuration is: Django 1.11, MySQL 5.6.35, mysqlclient 1.3.12, Redis 3.2.7 (x64), django-redis 4.9.0. -- Ticket URL: <https://code.djangoproject.com/ticket/29203#comment:6> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/064.b0e7436ac91997ea76ee583eef3526b4%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.