Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit f0cd0bf

Browse filesBrowse 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
Copy full SHA for f0cd0bf

File tree

Expand file treeCollapse file tree

1 file changed

+9
-2
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+9
-2
lines changed

‎components/debug.rst

Copy file name to clipboardExpand all lines: components/debug.rst
+9-2Lines changed: 9 additions & 2 deletions
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 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.