Fixed #28031 -- Removed notes about old uWSGI/sentry versions (refs #20537).

This commit is contained in:
Richard Barrell 2017-04-05 22:27:33 +01:00 committed by Tim Graham
parent 12d0567aa5
commit 351835f262
3 changed files with 0 additions and 24 deletions

View File

@ -81,10 +81,3 @@ application that later delegates to the Django WSGI application, if you want
to combine a Django application with a WSGI application of another framework. to combine a Django application with a WSGI application of another framework.
.. _`WSGI middleware`: https://www.python.org/dev/peps/pep-3333/#middleware-components-that-play-both-sides .. _`WSGI middleware`: https://www.python.org/dev/peps/pep-3333/#middleware-components-that-play-both-sides
.. note::
Some third-party WSGI middleware do not call ``close`` on the response
object after handling a request. In those cases the
:data:`~django.core.signals.request_finished` signal isn't sent. This can
result in idle connections to database and memcache servers.

View File

@ -34,15 +34,6 @@ command. For example:
.. _installation procedures: https://uwsgi-docs.readthedocs.io/en/latest/Install.html .. _installation procedures: https://uwsgi-docs.readthedocs.io/en/latest/Install.html
.. warning::
Some distributions, including Debian and Ubuntu, ship an outdated version
of uWSGI that does not conform to the WSGI specification. Versions prior to
1.2.6 do not call ``close`` on the response object after handling a
request. In those cases the :data:`~django.core.signals.request_finished`
signal isn't sent. This can result in idle connections to database and
memcache servers.
uWSGI model uWSGI model
----------- -----------

View File

@ -531,14 +531,6 @@ Arguments sent with this signal:
Sent when Django finishes delivering an HTTP response to the client. Sent when Django finishes delivering an HTTP response to the client.
.. note::
Some WSGI servers and middleware do not always call ``close`` on the
response object after handling a request, most notably uWSGI prior to 1.2.6
and Sentry's error reporting middleware up to 2.0.7. In those cases this
signal isn't sent at all. This can result in idle connections to database
and memcache servers.
Arguments sent with this signal: Arguments sent with this signal:
``sender`` ``sender``