'192b9bdd22ab9ed4d12e236c78afcb9a393ec15f71bbf5dc987d54727823bcbf'ĭo not reveal the secret key when posting questions or committing code. $ python -c 'import secrets print(secrets.token_hex())' ForĮxample, copy the output of this to your config: IfĪ secret key that will be used for securely signing the session cookieĪnd can be used for any other security related needs by extensions or yourĪpplication. This is a more specific version of TRAP_HTTP_EXCEPTIONS.
The error as an unhandled exception instead so that you get the interactiveĭebugger. Trying to access a key that doesn’t exist from request dicts like argsĪnd form will return a 400 Bad Request error page. To be handled by the interactive debugger instead of returning it as a If there is no handler for an HTTPException-type exception, re-raise it Request data on errors, and should normally not need to be set directly. If not set, this is implicitly true if TESTING or DEBUGĭefault: None PRESERVE_CONTEXT_ON_EXCEPTION ¶ĭon’t pop the request context when an exception occurs. You should enable this in your own tests.Įxceptions are re-raised rather than being handled by the app’s error Extensions may also change their behavior toįacilitate easier testing. Exceptions are propagated rather than handled by the
May not behave as expected if set in code.ĭo not enable debug mode when deploying in production.ĭefault: True if ENV is 'development', or FalseĮnable testing mode.
This is enabled when ENV is 'development'Īnd is overridden by the FLASK_DEBUG environment variable. The debug attribute maps to thisĬonfig key. Unhandled exceptions, and the server will be reloaded when codeĬhanges. When using flask run to start theĭevelopment server, an interactive debugger will be shown for
0 kommentar(er)
