@@ -155,23 +155,16 @@ For a full list of the options and their meaning, see the
155155
156156When you're in debug mode (the second argument of ``Kernel `` constructor in the
157157front controller is ``true ``), Symfony automatically adds an ``X-Symfony-Cache ``
158- header to the response. Use this to get information about cache hits and misses.
158+ header to the response. You can also use the ``trace_level `` config
159+ option and set it to either ``none ``, ``short `` or ``full `` to
160+ add this information.
159161
160- ..tip ::
161-
162- The ``trace_level `` config option can be set to ``none ``, ``short ``
163- and ``full `` to get different levels of information. When
164- configured explicitly, it works independent of the debug mode.
165-
166- ``short `` contains the information for the master request only.
167- It's written in a concise way that makes it easy to record the
168- information in your server log files. For example, in Apache you can
169- use ``%{X-Symfony-Cache}o `` in ``LogFormat `` format statements.
170-
171- With the information in your log files, you can use log processing
172- tools to extract general information about cache efficiency or
173- find out about URLs that have poor cache efficiency and might be
174- worth investigating.
162+ ``short `` will add the information for the master request only.
163+ It's written in a concise way that makes it easy to record the
164+ information in your server log files. For example, in Apache you can
165+ use ``%{X-Symfony-Cache}o `` in ``LogFormat `` format statements.
166+ This information can be used to extract general information about
167+ cache efficiency of your routes.
175168
176169..tip ::
177170
@@ -181,7 +174,7 @@ header to the response. Use this to get information about cache hits and misses.
181174..versionadded ::4.3
182175
183176 The ``trace_level `` and ``trace_header `` configuration options
184- wereadded in Symfony 4.3.
177+ wereintroduced in Symfony 4.3.
185178
186179.. _http-cache-symfony-versus-varnish :
187180