[1.8.x] Removed obsolete note about sentry/raven not handling WSGI properly.
2.0.7 was released in 2012.
Backport of 514fee82a1
from master
This commit is contained in:
parent
6bb8258255
commit
7e7e447b40
|
@ -85,7 +85,6 @@ to combine a Django application with a WSGI application of another framework.
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
Some third-party WSGI middleware do not call ``close`` on the response
|
Some third-party WSGI middleware do not call ``close`` on the response
|
||||||
object after handling a request — most notably Sentry's error reporting
|
object after handling a request. In those cases the
|
||||||
middleware up to version 2.0.7. In those cases the
|
|
||||||
:data:`~django.core.signals.request_finished` signal isn't sent. This can
|
:data:`~django.core.signals.request_finished` signal isn't sent. This can
|
||||||
result in idle connections to database and memcache servers.
|
result in idle connections to database and memcache servers.
|
||||||
|
|
Loading…
Reference in New Issue