#33152: Document the fact that a DB connection can be closed mid-request when a
HTTP client disconnects prematurely
-------------------------------------+-------------------------------------
Reporter: Rich | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| 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: Florian Apolloner (added)
* status: new => closed
* resolution: => invalid
* type: Uncategorized => Cleanup/optimization
Comment:
> I think the official doc needs to explain that a HTTP response can be
closed DURING the handling of a request - when this happens, seemingly
random django.db.utils.InterfaceErrors can be thrown.
`HttpResponse.close()` is called at the end of a request by the WSGI
server. I'm not sure what is calling `close()` in your case but I don't
see why and where Django is at fault. Handling of an HTTP request can be
interrupted in many ways and Django doesn't do anything unusual in this
matter. IMO, Django docs are not the best place to explain this.
--
Ticket URL: <https://code.djangoproject.com/ticket/33152#comment:1>
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/068.2f032559dc2cccf2d7f32e5905b842ea%40djangoproject.com.
