#3881: Don't mask server exception with session save exception
----------------------------------+------------------------------------
Reporter: hauserx@… | Owner: adrian
Type: Bug | Status: closed
Component: contrib.sessions | Version: 1.3-beta
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Changes (by Anssi Kääriäinen <akaariai@…>):
* status: reopened => closed
* resolution: => fixed
Comment:
In [aeda55e6bffc3cfbf53698af398a19c1a0f02d46]:
{{{
#!CommitTicketReference repository=""
revision="aeda55e6bffc3cfbf53698af398a19c1a0f02d46"
Fixed #3881 -- skip saving session when response status is 500
Saving session data is somewhat likely to lead into error when the
status code is 500. It is guaranteed to lead into error if the reason
for the 500 code is query error on PostgreSQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/3881#comment:9>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
