#29069: Static file serving does not call request_finished signal
-------------------------------------+-------------------------------------
Reporter: André | Owner: nobody
Cruz |
Type: Bug | Status: new
Component: HTTP | Version: 1.11
handling | Keywords: streamingresponse
Severity: Normal | request_finished
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
I'm using the method described here for serving uploaded files in
development:
https://docs.djangoproject.com/en/2.0/howto/static-files/#serving-files-
uploaded-by-a-user-during-development
However I've found that requests that hit these URLs emit the
request_started signal but not the request_finished signal. Supposedly
this signal would be sent after the content was sent but it is never sent.
I've tried both with runserver and the latest uWSGI.
This is a problem when we are using a connection pool since Django uses
this signal to cleanup db connections (and thus return them to the pool),
so we have a connection leak.
--
Ticket URL: <https://code.djangoproject.com/ticket/29069>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.5e6e83689e7375d7d3d6262b64c9a741%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
