#10554: Response.set_cookie should allow setting two cookies of the same name.
-------------------------------+------------------------------------
Reporter: Jeremy Dunck | Owner: nobody
Type: New feature | Status: new
Component: HTTP handling | Version: dev
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 Sarah Boyce):
* stage: Unreviewed => Accepted
Comment:
With the concern from raised from RFC6265 as to whether we should do this,
from what I read here:
https://datatracker.ietf.org/doc/html/rfc6265#section-5.3
> If the cookie store contains a cookie with the same name, domain, and
path as the newly created cookie... [instructions on how to replace]
I see no issue in two cookie's with the same name and uniqueness should be
determined by the combination of name, domain and path.
Based off how previously it was suggested this will be re-accepted
providing there is a real world use-case, re-accepting.
--
Ticket URL: <https://code.djangoproject.com/ticket/10554#comment:19>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f7b82d073-c89df73e-e311-4ec0-ae1b-31e6e5d3acf4-000000%40eu-central-1.amazonses.com.
