#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 Benjamin Vulpes):
* resolution: wontfix =>
* status: closed => new
Comment:
This is some serious bug necromancy, but hear me out.
My CDN supports presigned URLs and presigned cookies. Presigned URLs
negate client-side caching. Their presigned cookie implementation forbids
specifying more than one approved asset per cookie.
This forces me to include multiple of these presigned cookies for my CDN's
domain, with identical names, but paths for each asset, and to rely on the
browser to use cookies' paths to identify which version of the cookie to
send along with the request to the CDN.
Definitely an edge case, but worth bringing up as I can't find an escape
hatch to force Django to otherwise include cookies with the same name and
domain, but different paths.
--
Ticket URL: <https://code.djangoproject.com/ticket/10554#comment:17>
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/0107018f75d23315-87048b78-399c-48f2-ba16-fa7fdea71941-000000%40eu-central-1.amazonses.com.
