#36399: Missing cookies when using ASGI and HTTP/2
-------------------------------+------------------------------------
Reporter: Ingmar Stein | Owner: (none)
Type: New feature | Status: new
Component: HTTP handling | Version: 5.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by Carlton Gibson):
* cc: Carlton Gibson (removed)
* easy: 0 => 1
* type: Bug => New feature
Comment:
Yes, I confirm this.
`ASGIRequest` will need to special case the cookie header in a similar way
to how it handles content-length &co before entering the _generic headers_
loop.
Multiple cookie values need to be joined with semicolons — which are
already present terminating the value — not commas.
Looks like HTTP/1 didn't allow multiple Cookie headers, and they had to be
automatically grouped by the client, where HTTP/2 does allow this.
Since this has never been supported I'll mark it a new feature: it
probably merits a line in the release notes.
--
Ticket URL: <https://code.djangoproject.com/ticket/36399#comment:2>
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 visit
https://groups.google.com/d/msgid/django-updates/01070196d46e3b85-f36cab2e-4a80-410b-89f0-8f6b71162532-000000%40eu-central-1.amazonses.com.
