|
|
|
@ -89,13 +89,15 @@ The following configuration values are used internally by Flask:
|
|
|
|
|
helpful for hairy debugging situations |
|
|
|
|
where you have to find out where an HTTP |
|
|
|
|
exception is coming from. |
|
|
|
|
``TRAP_BAD_REQUEST_KEY_ERRORS`` Werkzeug's internal data structures that |
|
|
|
|
``TRAP_BAD_REQUEST_ERRORS`` Werkzeug's internal data structures that |
|
|
|
|
deal with request specific data will |
|
|
|
|
raise special key errors that are also |
|
|
|
|
bad request exceptions. By default |
|
|
|
|
these will be converted into 400 |
|
|
|
|
responses which however can make |
|
|
|
|
debugging some issues harder. If this |
|
|
|
|
bad request exceptions. Likewise many |
|
|
|
|
operations can implicitly fail with a |
|
|
|
|
BadRequest exception for consistency. |
|
|
|
|
Since it's nice for debugging to know |
|
|
|
|
why exactly it failed this flag can be |
|
|
|
|
used to debug those situations. If this |
|
|
|
|
config is set to ``True`` you will get |
|
|
|
|
a regular traceback instead. |
|
|
|
|
================================= ========================================= |
|
|
|
@ -132,7 +134,7 @@ The following configuration values are used internally by Flask:
|
|
|
|
|
``PROPAGATE_EXCEPTIONS``, ``PRESERVE_CONTEXT_ON_EXCEPTION`` |
|
|
|
|
|
|
|
|
|
.. versionadded:: 0.8 |
|
|
|
|
``TRAP_BAD_REQUEST_KEY_ERRORS``, ``TRAP_HTTP_EXCEPTIONS`` |
|
|
|
|
``TRAP_BAD_REQUEST_ERRORS``, ``TRAP_HTTP_EXCEPTIONS`` |
|
|
|
|
|
|
|
|
|
Configuring from Files |
|
|
|
|
---------------------- |
|
|
|
|