#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 Nico Giefing):
* status: closed => new
* resolution: needsinfo =>
Comment:
As described in the RFC, in a cookie value a backslash "\" is not to be
used.
The issue is that a " will be seen as the end of the cookie value on every
device in the middle (WAF) and therefore not the full cookie value will
get through to the webserver.
Please let me know if you need more guidance.
--
Ticket URL: <https://code.djangoproject.com/ticket/32191#comment:3>
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.80ba579b1e9e783c418293b088e26511%40djangoproject.com.
