mirror of
https://github.com/django/django.git
synced 2025-08-04 10:59:45 +00:00
Fixed #19519 -- Fired request_finished in the WSGI iterable's close().
This commit is contained in:
parent
a53c474026
commit
acc5396e6d
9 changed files with 111 additions and 20 deletions
|
@ -790,6 +790,8 @@ types of HTTP responses. Like ``HttpResponse``, these subclasses live in
|
|||
:class:`~django.template.response.SimpleTemplateResponse`, and the
|
||||
``render`` method must itself return a valid response object.
|
||||
|
||||
.. _httpresponse-streaming:
|
||||
|
||||
StreamingHttpResponse objects
|
||||
=============================
|
||||
|
||||
|
|
|
@ -448,6 +448,18 @@ request_finished
|
|||
|
||||
Sent when Django finishes processing an HTTP request.
|
||||
|
||||
.. note::
|
||||
|
||||
When a view returns a :ref:`streaming response <httpresponse-streaming>`,
|
||||
this signal is sent only after the entire response is consumed by the
|
||||
client (strictly speaking, by the WSGI gateway).
|
||||
|
||||
.. versionchanged:: 1.5
|
||||
|
||||
Before Django 1.5, this signal was fired before sending the content to the
|
||||
client. In order to accomodate streaming responses, it is now fired after
|
||||
sending the content.
|
||||
|
||||
Arguments sent with this signal:
|
||||
|
||||
``sender``
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue