summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2020-09-09 08:28:08 +0200
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2020-09-09 09:35:56 +0200
commit4e6b6fac438518b12b1e5d29fa019cc4f6251ebf (patch)
tree1efdeb144f515575376d2ed07ae7e44343c43c04 /docs/ref
parent3fc636244e07c02645fcebda769d7adf4ab560a6 (diff)
[3.1.x] Mentioned ASGI handler in SuspiciousOperation docs.
Backport of 453967477e3ddae704cd739eac2449c0e13d464c from master
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/exceptions.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/ref/exceptions.txt b/docs/ref/exceptions.txt
index 4b1837b632..5c2f4b8b66 100644
--- a/docs/ref/exceptions.txt
+++ b/docs/ref/exceptions.txt
@@ -85,8 +85,8 @@ Django core exception classes are defined in ``django.core.exceptions``.
* ``SuspiciousSession``
* ``TooManyFieldsSent``
- If a ``SuspiciousOperation`` exception reaches the WSGI handler level it is
- logged at the ``Error`` level and results in
+ If a ``SuspiciousOperation`` exception reaches the ASGI/WSGI handler level
+ it is logged at the ``Error`` level and results in
a :class:`~django.http.HttpResponseBadRequest`. See the :doc:`logging
documentation </topics/logging/>` for more information.