summaryrefslogtreecommitdiff
path: root/docs/ref/exceptions.txt
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:05:28 +0200
commit453967477e3ddae704cd739eac2449c0e13d464c (patch)
tree7bb7bb97d9492dffc45d5e3964842eb756db20be /docs/ref/exceptions.txt
parent2808cdc8fb15ad27f83af3e62db69f5ea7ced29e (diff)
Mentioned ASGI handler in SuspiciousOperation docs.
Diffstat (limited to 'docs/ref/exceptions.txt')
-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 d4af1de79d..2f5aa64b9d 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.