Skip to content

Commit 0d2bf4f

Browse files
committed
Merge branch '2.4' into 2.5
* 2.4: Route description correction. Link to FOSHttpCacheBundle fixes environment/application mistake
2 parents cea3fa6 + a7738ca commit 0d2bf4f

File tree

3 files changed

+15
-5
lines changed

3 files changed

+15
-5
lines changed

book/page_creation.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ the new route that defines the URL of the page that you're about to create:
231231
The routing consists of two basic pieces: the ``path``, which is the URL
232232
that this route will match, and a ``defaults`` array, which specifies the
233233
controller that should be executed. The placeholder syntax in the path
234-
(``{limit}``) is a wildcard. It means that ``/number/10``, ``/number/327``
234+
(``{limit}``) is a wildcard. It means that ``/random/10``, ``/random/327``
235235
or any other similar URL will match this route. The ``{limit}`` placeholder
236236
parameter will also be passed to the controller so that you can use its value
237237
to generate the proper random number.

cookbook/cache/varnish.rst

+13-3
Original file line numberDiff line numberDiff line change
@@ -91,10 +91,18 @@ Symfony2 adds automatically:
9191
Cache Invalidation
9292
------------------
9393

94-
You should never need to invalidate cached data because invalidation is already
95-
taken into account natively in the HTTP cache models (see :ref:`http-cache-invalidation`).
94+
If you want to cache content that changes frequently and still serve
95+
the most recent version to users, you need to invalidate that content.
96+
While `cache invalidation`_ allows you to purge content from your
97+
proxy before it has expired, it adds complexity to your caching setup.
9698

97-
Still, Varnish can be configured to accept a special HTTP ``PURGE`` method
99+
.. tip::
100+
101+
The open source `FOSHttpCacheBundle`_ takes the pain out of cache
102+
invalidation by helping you to organize your caching and
103+
invalidation setup.
104+
105+
Varnish can be configured to accept a special HTTP ``PURGE`` method
98106
that will invalidate the cache for a given resource:
99107

100108
.. code-block:: text
@@ -232,3 +240,5 @@ absolute URLs:
232240
.. _`Edge Architecture`: http://www.w3.org/TR/edge-arch
233241
.. _`GZIP and Varnish`: https://www.varnish-cache.org/docs/3.0/phk/gzip.html
234242
.. _`Surrogate-Capability Header`: http://www.w3.org/TR/edge-arch
243+
.. _`cache invalidation`: http://tools.ietf.org/html/rfc2616#section-13.10
244+
.. _`FOSHttpCacheBundle`: http://foshttpcachebundle.readthedocs.org/

cookbook/configuration/environments.rst

+1-1
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,7 @@ used by each is explicitly set::
153153

154154
// ...
155155

156-
As you can see, the ``prod`` key specifies that this environment will run
156+
As you can see, the ``prod`` key specifies that this application will run
157157
in the ``prod`` environment. A Symfony2 application can be executed in any
158158
environment by using this code and changing the environment string.
159159

0 commit comments

Comments
 (0)