#34173: SessionMiddleware support 503 status code
----------------------------------+--------------------------------------
Reporter: SessionIssue | Owner: nobody
Type: New feature | Status: new
Component: contrib.sessions | Version: 4.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by SessionIssue):
Replying to [comment:3 Mariusz Felisiak]:
> I'm not sure why we should treat 503 differently. IMO, we could
reconsider avoiding session saving when status code > 500 🤔
>
> PS. Do not reopen tickets without further explanation.
That would fix the problem and seems like a convenient solution to me.
Thanks a lot! 😁
--
Ticket URL: <https://code.djangoproject.com/ticket/34173#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/010701849ef41114-04a5057a-8c75-4fad-ac4d-db4254bcaf6b-000000%40eu-central-1.amazonses.com.
