Built-in Symfony Events¶

During the handling of an HTTP request, the Symfony framework (or any application using the HttpKernel component) dispatches some events which you can use to modify how the request is handled.

Kernel Events¶

Each event dispatched by the HttpKernel component is a subclass of KernelEvent, which provides the following information:

getRequestType(): Returns the type of the request (HttpKernelInterface::MASTER_REQUEST or HttpKernelInterface::SUB_REQUEST).
getKernel(): Returns the Kernel handling the request.
getRequest(): Returns the current Request being handled.
isMasterRequest(): Checks if this is a master request.

`kernel.request`¶

Event Class: RequestEvent

This event is dispatched very early in Symfony, before the controller is determined. It’s useful to add information to the Request or return a Response early to stop the handling of the request.

See also

`kernel.controller`¶

Event Class: ControllerEvent

This event is dispatched after the controller to be executed has been resolved but before executing it. It’s useful to initialize things later needed by the controller, such as param converters, and even to change the controller entirely:

use Symfony\Component\HttpKernel\Event\ControllerEvent;

public function onKernelController(ControllerEvent $event)
{
    // ...

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

See also

Read more on the kernel.controller event.

Execute this command to find out which listeners are registered for this event and their priorities:

1	$ php bin/console debug:event-dispatcher kernel.controller

`kernel.controller_arguments`¶

Event Class: ControllerArgumentsEvent

This event is dispatched just before a controller is called. It’s useful to configure the arguments that are going to be passed to the controller. Typically, this is used to map URL routing parameters to their corresponding named arguments; or pass the current request when the Request type-hint is found:

use Symfony\Component\HttpKernel\Event\ControllerArgumentsEvent;

public function onKernelControllerArguments(ControllerArgumentsEvent $event)
{
    // ...

    // get controller and request arguments
    $namedArguments = $event->getRequest()->attributes->all();
    $controllerArguments = $event->getArguments();

    // set the controller arguments to modify the original arguments or add new ones
    $event->setArguments($newArguments);
}

Execute this command to find out which listeners are registered for this event and their priorities:

1	$ php bin/console debug:event-dispatcher kernel.controller_arguments

`kernel.view`¶

Event Class: ViewEvent

This event is dispatched after the controller has been executed but only if the controller does not return a Response object. It’s useful to transform the returned value (e.g. a string with some HTML contents) into the Response object needed by Symfony:

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

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

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

    $event->setResponse($response);
}

See also

`kernel.response`¶

Event Class: ResponseEvent

This event is dispatched after the controller or any kernel.view listener returns a Response object. It’s useful to modify or replace the response before sending it back (e.g. add/modify HTTP headers, add cookies, etc.):

use Symfony\Component\HttpKernel\Event\ResponseEvent;

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

    // ... modify the response object
}

See also

`kernel.finish_request`¶

Event Class: FinishRequestEvent

This event is dispatched after the kernel.response event. It’s useful to reset the global state of the application (for example, the translator listener resets the translator’s locale to the one of the parent request):

use Symfony\Component\HttpKernel\Event\FinishRequestEvent;

public function onKernelFinishRequest(FinishRequestEvent $event)
{
    if (null === $parentRequest = $this->requestStack->getParentRequest()) {
        return;
    }

    // reset the locale of the subrequest to the locale of the parent request
    $this->setLocale($parentRequest);
}

Execute this command to find out which listeners are registered for this event and their priorities:

1	$ php bin/console debug:event-dispatcher kernel.finish_request

`kernel.terminate`¶

Event Class: TerminateEvent

This event is dispatched after the response has been sent (after the execution of the handle() method). It’s useful to perform slow or complex tasks that don’t need to be completed to send the response (e.g. sending emails).

See also

Read more on the kernel.terminate event.

Execute this command to find out which listeners are registered for this event and their priorities:

1	$ php bin/console debug:event-dispatcher kernel.terminate

`kernel.exception`¶

Event Class: ExceptionEvent

This event is dispatched as soon as an error occurs during the handling of the HTTP request. It’s useful to recover from errors or modify the exception details sent as response:

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

public function onKernelException(ExceptionEvent $event)
{
    $exception = $event->getThrowable();
    $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->setThrowable($exception);
}

Note

The TwigBundle registers an ExceptionListener that forwards the Request to a given controller defined by the exception_listener.controller parameter.

Symfony uses the following logic to determine the HTTP status code of the response:

If isClientError(), isServerError() or isRedirect() is true, then the status code on your Response object is used;
If the original exception implements HttpExceptionInterface, then getStatusCode() is called on the exception and used (the headers from getHeaders() are also added);
If both of the above aren’t true, then a 500 status code is used.

Note

If you want to overwrite the status code of the exception response, which you should not without a good reason, call ExceptionEvent::allowCustomResponseCode() first and then set the status code on the response:

$event->allowCustomResponseCode();
$response = new Response('No Content', 204);
$event->setResponse($response);

The status code sent to the client in the above example will be 204. If $event->allowCustomResponseCode() is omitted, then the kernel will set an appropriate status code based on the type of exception thrown.

See also

Read more on the kernel.exception event.

Execute this command to find out which listeners are registered for this event and their priorities:

1	$ php bin/console debug:event-dispatcher kernel.exception

Built-in Symfony Events¶

Kernel Events¶

kernel.request¶

kernel.controller¶

kernel.controller_arguments¶

kernel.view¶

kernel.response¶

kernel.finish_request¶

kernel.terminate¶

kernel.exception¶

`kernel.request`¶

`kernel.controller`¶

`kernel.controller_arguments`¶

`kernel.view`¶

`kernel.response`¶

`kernel.finish_request`¶

`kernel.terminate`¶

`kernel.exception`¶