#32191: Not RFC 6265 compliant cookies in contrib.messages.
----------------------------------+------------------------------------
Reporter: Nico Giefing | Owner: nobody
Type: Bug | Status: new
Component: contrib.messages | Version: 3.1
Severity: Normal | Resolution:
Keywords: Cookie malformed | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Florian Apolloner):
Well technically it applies to the whole `request.cookies` interface; but
I don't see any feasible fix there. It would a) be highly backwards
incompatible and b) cookies might require coordination with the frontend
JS -- so it is better if the user can decide what to encode and how. I
mean in the best case one doesn't store much in cookies either way, they
do not perform well with concurrent requests for instance…
--
Ticket URL: <https://code.djangoproject.com/ticket/32191#comment:8>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.c5e5b11e474876020de4641483b5f681%40djangoproject.com.
