Skip to content

Commit f0cd0bf

Browse files
greg0irejaviereguiluz
authored andcommitted
Recommend registering the error handler in prod
This is what currently happens when using Symfony in a standard way, and people have been wondering online about alarming exceptions from the Debug component in production. See https://stackoverflow.com/questions/37431935/is-it-normal-to-have-symfony-component-debug-exception-fatalerrorexception-excep
1 parent ba40eff commit f0cd0bf

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

components/debug.rst

+9-2
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,9 @@ tools.
3737

3838
.. caution::
3939

40-
You should never enable the debug tools in a production environment as
41-
they might disclose sensitive information to the user.
40+
Apart from the error handler, you should never enable the debug
41+
tools in a production environment as they might disclose sensitive
42+
information to the user.
4243

4344
Enabling the Error Handler
4445
--------------------------
@@ -52,6 +53,12 @@ fatal errors)::
5253

5354
ErrorHandler::register();
5455

56+
.. note::
57+
58+
This one is fine to use in a production environment and will be
59+
enabled if you use the framework bundle, so that you get better
60+
logging.
61+
5562
Enabling the Exception Handler
5663
------------------------------
5764

0 commit comments

Comments
 (0)