innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Described DEBUG_PROPAGATE_EXCEPTIONS behavior in more detail.

This commit is contained in:
Tim Graham 2017-03-09 11:55:14 -05:00
parent dfbdba924f
commit c577d8a498
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/ref/settings.txt
View File

@ -1097,10 +1097,15 @@ requests being returned as "Bad Request (400)".
Default: ``False`` Default: ``False``
If set to True, Django's normal exception handling of view functions If set to ``True``, Django's exception handling of view functions
will be suppressed, and exceptions will propagate upwards. This can (:data:`~django.conf.urls.handler500`, or the debug view if :setting:`DEBUG`
be useful for some test setups, and should never be used on a live is ``True``) and logging of 500 responses (:ref:`django-request-logger`) is
site. skipped and exceptions propagate upwards.
This can be useful for some test setups. It shouldn't be used on a live site
unless you want your web server (instead of Django) to generate "Internal
Server Error" responses. In that case, make sure your server doesn't show the
stack trace or other sensitive information in the response.
.. setting:: DECIMAL_SEPARATOR .. setting:: DECIMAL_SEPARATOR