Fixed #19519 -- Fired request_finished in the WSGI iterable's close().

2 files changed, 14 insertions, 0 deletions

diff --git a/docs/ref/request-response.txt b/docs/ref/request-response.txt
index ae1da6cb4b..a8e0ef3f51 100644
--- a/docs/ref/request-response.txt
+++ b/docs/ref/request-response.txt
@@ -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
 =============================
 
diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index b27a4f87cc..f2f1459bf0 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -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``