#27328: return `Set-Cookie` if sessionid= None value -------------------------------------+------------------------------------- Reporter: Ramin Farajpour | Owner: nobody Cami | Type: Bug | Status: new Component: contrib.sessions | Version: 1.10 Severity: Normal | Resolution: Keywords: | Triage Stage: | Unreviewed Has patch: 1 | Needs documentation: 0 Needs tests: 1 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Collin Anderson): This change is growing on me. It does seem a hair more beginner friendly. I also wish I understood the use case better. Ramin: how is the current behavior problematic? Why is this an issue? What's so bad about the `Set- Cookie` header in this case? -- Ticket URL: <https://code.djangoproject.com/ticket/27328#comment:20> 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/065.23275a241cfe1d7c772998da1b86fadc%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.