#32191: Not RFC Compliant Cookie handling
----------------------------------+--------------------------------------
Reporter: Nico Giefing | Owner: nobody
Type: Bug | Status: new
Component: HTTP handling | Version: 3.1
Severity: Normal | Resolution:
Keywords: Cookie malformed | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by Florian Apolloner):
* status: closed => new
* resolution: wontfix =>
Comment:
Given that you CC'ed me I am going to reopen this :) The spec is rather
clear on what is allowed and we should try (when we generate cookies) to
comply. This should at least apply to cookies Django core/contrib apps
(d.c.messages) generates. I am not sure if we want to put encoding
handling into our general cookie handling; I'd probably leave that to the
enduser if they want to store weird data there :D
--
Ticket URL: <https://code.djangoproject.com/ticket/32191#comment:5>
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/063.0db086e71ff074c744e5cf3a1dfa6ec3%40djangoproject.com.
