Book Image

Mastering Symfony

Book Image

Mastering Symfony

Overview of this book

In this book, you will learn some lesser known aspects of development with Symfony, and you will see how to use Symfony as a framework to create reliable and effective applications. You might have developed some impressive PHP libraries in other projects, but what is the point when your library is tied to one particular project? With Symfony, you can turn your code into a service and reuse it in other projects. This book starts with Symfony concepts such as bundles, routing, twig, doctrine, and more, taking you through the request/response life cycle. You will then proceed to set up development, test, and deployment environments in AWS. Then you will create reliable projects using Behat and Mink, and design business logic, cover authentication, and authorization steps in a security checking process. You will be walked through concepts such as DependencyInjection, service containers, and services, and go through steps to create customized commands for Symfony's console. Finally, the book covers performance optimization and the use of Varnish and Memcached in our project, and you are treated with the creation of database agnostic bundles and best practices.
Table of Contents (17 chapters)
Mastering Symfony
Credits
About the Author
About the Reviewers
Index

Using the Symfony reverse proxy cache


There is no complicated or lengthy procedure required to activate Symfony's gateway cache. Just open the front controller and uncomment the following lines:

// web/app.php
<?php
//...
require_once __DIR__.'/../app/AppKernel.php';
//un comment this line
require_once __DIR__.'/../app/AppCache.php';  
$kernel = new AppKernel('prod', false);
$kernel->loadClassCache();
// and this line
$kernel = new AppCache($kernel);            
// ...
?>

Now, the kernel is wrapped around the Application Cache layer, which means that any request coming from the client will pass through this layer first.

Set expiration for dashboard page

Log in to your project, and in the debug toolbar, click on the request section. Then, scroll down to the Response header and check the contents:

As you can see, only Cache-Control is sitting here with some default values among the cache headers that we are interested in.

When you don't set any value for Cache-Control, Symfony considers...