#34571: Request with invalid session after concurrent logout or session timeout
is
considered a BadRequest
-------------------------------------+-------------------------------------
Reporter: Daniel Nunes | Owner: Daniel
Type: | Nunes
Cleanup/optimization | Status: closed
Component: contrib.sessions | Version: 3.2
Severity: Normal | Resolution: wontfix
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 Mariusz Felisiak):
* cc: Carlton Gibson (added)
* status: assigned => closed
* resolution: => wontfix
Comment:
I appreciate you'd like to reopen the ticket, but less than 1 day of
discussion and 1 vote is not enough to reopen a ticket. Let's wait few
more days.
Also, take into account that `PermissionDenied` subclasses are
[https://github.com/django/django/blob/93830abf7694e0f281931f10eeaa34993855e7dd/django/core/handlers/exception.py#L72-L82
treated] differently than `BadRequest`
[https://github.com/django/django/blob/93830abf7694e0f281931f10eeaa34993855e7dd/django/core/handlers/exception.py#L96-L112
subclasses].
--
Ticket URL: <https://code.djangoproject.com/ticket/34571#comment:7>
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/010701882968a6c8-a44d17c8-ea70-4a4c-92b6-cbaa2a59eb4f-000000%40eu-central-1.amazonses.com.
