summaryrefslogtreecommitdiff
path: root/docs/howto
diff options
context:
space:
mode:
authorRichard Barrell <richard@brrll.co.uk>2017-04-05 22:27:33 +0100
committerTim Graham <timograham@gmail.com>2017-04-06 09:34:11 -0400
commit0cb009aa488f4c66d2b434bf3df13e719b2e2fc6 (patch)
tree82fc2ea6e204e4724f6cfe30b23d39a8be1cc501 /docs/howto
parent44bf3c6812a42360bd22741a5943145527ce4acf (diff)
[1.11.x] Fixed #28031 -- Removed notes about old uWSGI/sentry versions (refs #20537).
Backport of 351835f26234cade43f0bed45441fc144c33a785 from master
Diffstat (limited to 'docs/howto')
-rw-r--r--docs/howto/deployment/wsgi/index.txt7
-rw-r--r--docs/howto/deployment/wsgi/uwsgi.txt9
2 files changed, 0 insertions, 16 deletions
diff --git a/docs/howto/deployment/wsgi/index.txt b/docs/howto/deployment/wsgi/index.txt
index 214ebc54a4..282ab10af6 100644
--- a/docs/howto/deployment/wsgi/index.txt
+++ b/docs/howto/deployment/wsgi/index.txt
@@ -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.
.. _`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.
diff --git a/docs/howto/deployment/wsgi/uwsgi.txt b/docs/howto/deployment/wsgi/uwsgi.txt
index b026a31d4a..e21adbb990 100644
--- a/docs/howto/deployment/wsgi/uwsgi.txt
+++ b/docs/howto/deployment/wsgi/uwsgi.txt
@@ -34,15 +34,6 @@ command. For example:
.. _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
-----------