#32191: Not RFC 6265 compliant cookies in contrib.messages.
----------------------------------+---------------------------------------
Reporter: Nico Giefing | Owner: Craig Smith
Type: Bug | Status: assigned
Component: contrib.messages | Version: 3.1
Severity: Normal | Resolution:
Keywords: Cookie malformed | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+---------------------------------------
Comment (by Florian Apolloner):
Hi Craig,
I've looked through your pull request and I finally understand why you
needed the bunch of encode/decode stuff everywhere. Personally as a result
of that I think the code is now rather ugly (certainly not your fault, but
rather ours since we have a mix of bytes and strings everywhere here). I
have an idea that I want to try out to directly use signing.loads/dumps in
the message cookie backend; which might make this all (a bit?) easier.
I'll try to put something up as a draft PR and maybe we can find a nice
way out of this mess :)
--
Ticket URL: <https://code.djangoproject.com/ticket/32191#comment:26>
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.0024e02035bdb82496e69842950b2959%40djangoproject.com.
