#34571: Request with invalid session after concurrent logout or session timeout
is
considered a BadRequest
-------------------------------------+-------------------------------------
Reporter: Daniel Nunes | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.sessions | Version: 3.2
Severity: Normal | Resolution:
Keywords: session, session | Triage Stage:
bad request | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Daniel Nunes):
* status: closed => new
* resolution: wontfix =>
Comment:
After discussing the ticket [https://forum.djangoproject.com/t/request-
with-invalid-session-after-concurrent-logout-or-session-timeout-is-
considered-a-badrequest/20980 here] with Carlton, I will re-open the
ticket. I'll also assign it to myself.
Thank you!
--
Ticket URL: <https://code.djangoproject.com/ticket/34571#comment:4>
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/01070188296230de-7e94d646-d371-4fbd-970e-94eaafd82ceb-000000%40eu-central-1.amazonses.com.
