Permalink
Browse files

bug #3634 Fix goal of “framework.profiler.only_exceptions“ option whi…

…ch profile on each exceptions on controller (not only 500) (stephpy)

This PR was submitted for the master branch but it was merged into the 2.3 branch instead (closes #3634).

Discussion
----------

Fix goal of “framework.profiler.only_exceptions“ option which profile on each exceptions on controller (not only 500)

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | 2.*

See symfony/symfony#10375 (comment)

Commits
-------

0ea5639 Fix goal of “framework.profiler.only_exceptions“ option which profile on each exceptions on controller (not only 500)
  • Loading branch information...
weaverryan committed Mar 19, 2014
2 parents db3cde7 + 2ed16bc commit 9fcccc734fdda2aa07ee2ced0da88c3c86f006a8
Showing with 1 addition and 1 deletion.
  1. +1 −1 book/internals.rst
View
@@ -644,7 +644,7 @@ If you enable the web profiler, you also need to mount the profiler routes:
As the profiler adds some overhead, you might want to enable it only under
certain circumstances in the production environment. The ``only_exceptions``
settings limits profiling to 500 pages, but what if you want to get
settings limits profiling to exceptions, but what if you want to get
information when the client IP comes from a specific address, or for a limited
portion of the website? You can use a Profiler Matcher, learn more about that
in ":doc:`/cookbook/profiler/matchers`".

0 comments on commit 9fcccc7

Please sign in to comment.