diff options
| author | Tim Graham <timograham@gmail.com> | 2017-03-09 11:55:14 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2017-03-09 14:04:29 -0500 |
| commit | e9e58ec65e949fb6cf46cdf90a24180e98cbd65a (patch) | |
| tree | 005f9f56093879946b9b2aea194cd9384bddbaf1 /docs | |
| parent | e9ba8563c115ea331e7fb52b26ddb9cced5c7c94 (diff) | |
[1.11.x] Described DEBUG_PROPAGATE_EXCEPTIONS behavior in more detail.
Backport of c577d8a4981233b4d0f65c6ce57ae33d304095b9 from master
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/settings.txt | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index e9c333081a..6cab03f3c2 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -1106,10 +1106,15 @@ requests being returned as "Bad Request (400)". Default: ``False`` -If set to True, Django's normal exception handling of view functions -will be suppressed, and exceptions will propagate upwards. This can -be useful for some test setups, and should never be used on a live -site. +If set to ``True``, Django's exception handling of view functions +(:data:`~django.conf.urls.handler500`, or the debug view if :setting:`DEBUG` +is ``True``) and logging of 500 responses (:ref:`django-request-logger`) is +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 |