#27604: Use set_signed_cookie for contrib.messages Cookie storage --------------------------------------+------------------------------------ Reporter: Anthony King | Owner: nobody Type: Cleanup/optimization | Status: new Component: contrib.messages | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 --------------------------------------+------------------------------------ Changes (by Tim Graham):
* stage: Unreviewed => Accepted Comment: I haven't investigated but since `contrib.messages` was added in 2009 and `set_signed_cookie()` in 2011, there probably wasn't an intentional change not to use it. I guess a deprecation period that offers backwards- compatibility for the old format will be needed. -- Ticket URL: <https://code.djangoproject.com/ticket/27604#comment:1> 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/067.c70b88c83101e481215d7f7411a56d95%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.