diff options
| author | Richard Barrell <richard@brrll.co.uk> | 2017-04-05 22:27:33 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2017-04-06 09:09:49 -0400 |
| commit | 351835f26234cade43f0bed45441fc144c33a785 (patch) | |
| tree | 5a2e6f4443ba7439445b169713c7e3e746bddec8 /docs | |
| parent | 12d0567aa5e82322543f0c0c126ba18c91a1e439 (diff) | |
Fixed #28031 -- Removed notes about old uWSGI/sentry versions (refs #20537).
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/howto/deployment/wsgi/index.txt | 7 | ||||
| -rw-r--r-- | docs/howto/deployment/wsgi/uwsgi.txt | 9 | ||||
| -rw-r--r-- | docs/ref/signals.txt | 8 |
3 files changed, 0 insertions, 24 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 ----------- diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt index 58026d9425..dc5bfd943b 100644 --- a/docs/ref/signals.txt +++ b/docs/ref/signals.txt @@ -531,14 +531,6 @@ Arguments sent with this signal: 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: ``sender`` |