p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #32535 -- Added note about DEBUG_PROPAGATE_EXCEPTIONS setting to middleware docs.

This commit is contained in:
Hasan Ramezani 2021-04-09 13:17:46 +04:30 committed by GitHub
parent e84b054325
commit fc268c8648
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/topics/http/middleware.txt
View File

@ -286,6 +286,9 @@ if the very next middleware in the chain raises an
that exception; instead it will get an :class:`~django.http.HttpResponse` that exception; instead it will get an :class:`~django.http.HttpResponse`
object with a :attr:`~django.http.HttpResponse.status_code` of 404. object with a :attr:`~django.http.HttpResponse.status_code` of 404.
You can set :setting:`DEBUG_PROPAGATE_EXCEPTIONS` to ``True`` to skip this
conversion and propagate exceptions upwards.
.. _async-middleware: .. _async-middleware:
Asynchronous support Asynchronous support