kernel.request¶

Event Class: Symfony\Component\HttpKernel\Event\GetResponseEvent

This event is dispatched very early in Symfony, before the controller is determined.

These are the built-in Symfony listeners registered to this event:

kernel.controller¶

Event Class: Symfony\Component\HttpKernel\Event\FilterControllerEvent

This event can be an entry point used to modify the controller that should be executed:

use Symfony\Component\HttpKernel\Event\FilterControllerEvent;

public function onKernelController(FilterControllerEvent $event)
{
    $controller = $event->getController();
    // ...

    // the controller can be changed to any PHP callable
    $event->setController($controller);
}

This is the built-in Symfony listener related to this event:

kernel.view¶

Event Class: Symfony\Component\HttpKernel\Event\GetResponseForControllerResultEvent

This event is not used by the FrameworkBundle, but it can be used to implement a view sub-system. This event is called only if the Controller does not return a Response object. The purpose of the event is to allow some other return value to be converted into a Response.

The value returned by the Controller is accessible via the getControllerResult method:

use Symfony\Component\HttpKernel\Event\GetResponseForControllerResultEvent;
use Symfony\Component\HttpFoundation\Response;

public function onKernelView(GetResponseForControllerResultEvent $event)
{
    $val = $event->getControllerResult();
    $response = new Response();

    // ... somehow customize the Response from the return value

    $event->setResponse($response);
}

kernel.response¶

Event Class: Symfony\Component\HttpKernel\Event\FilterResponseEvent

The purpose of this event is to allow other systems to modify or replace the Response object after its creation:

public function onKernelResponse(FilterResponseEvent $event)
{
    $response = $event->getResponse();

    // ... modify the response object
}

The FrameworkBundle registers several listeners:

Symfony\Component\HttpKernel\EventListener\ProfilerListener

Collects data for the current request.

Symfony\Bundle\WebProfilerBundle\EventListener\WebDebugToolbarListener

Injects the Web Debug Toolbar.

Symfony\Component\HttpKernel\EventListener\ResponseListener

Fixes the Response Content-Type based on the request format.

Symfony\Component\HttpKernel\EventListener\EsiListener

Adds a Surrogate-Control HTTP header when the Response needs to be parsed for ESI tags.

These are the built-in Symfony listeners registered to this event:

kernel.terminate¶

Event Class: Symfony\Component\HttpKernel\Event\PostResponseEvent

The purpose of this event is to perform tasks after the response was already served to the client.

This is the built-in Symfony listener related to this event:

kernel.exception¶

Event Class: Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent

The TwigBundle registers an Symfony\Component\HttpKernel\EventListener\ExceptionListener that forwards the Request to a given controller defined by the exception_listener.controller parameter.

A listener on this event can create and set a Response object, create and set a new Exception object, or do nothing:

use Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent;
use Symfony\Component\HttpFoundation\Response;

public function onKernelException(GetResponseForExceptionEvent $event)
{
    $exception = $event->getException();
    $response = new Response();
    // setup the Response object based on the caught exception
    $event->setResponse($response);

    // you can alternatively set a new Exception
    // $exception = new \Exception('Some special exception');
    // $event->setException($exception);
}

$response = new Response(
    'Error',
    404, // this status code will be ignored
    array(
        'X-Status-Code' => 200 // this status code will actually be sent to the client
    )
);

These are the built-in Symfony listeners registered to this event: