Middleware

    A middleware implements the PSR-15 Middleware Interface:

    • - The PSR-7 request object
    • Psr\Http\Server\RequestHandlerInterface - The PSR-15 request handler objectIt can do whatever is appropriate with these objects. The only hard requirementis that a middleware MUST return an instance of Psr\Http\Message\ResponseInterface.Each middleware SHOULD invoke the next middleware and pass it Request andResponse objects as arguments.

    Different frameworks use middleware differently. Slim adds middleware as concentriclayers surrounding your core application. Each new middleware layer surroundsany existing middleware layers. The concentric structure expands outwardly asadditional middleware layers are added.

    The last middleware layer added is the first to be executed.

    When you run the Slim application, the Request object traverses themiddleware structure from the outside in. They first enter the outer-most middleware,then the next outer-most middleware, (and so on), until they ultimately arriveat the Slim application itself. After the Slim application dispatches theappropriate route, the resultant Response object exits the Slim application andtraverses the middleware structure from the inside out. Ultimately, a finalResponse object exits the outer-most middleware, is serialized into a raw HTTPresponse, and is returned to the HTTP client. Here’s a diagram that illustratesthe middleware process flow:

    Middleware is a callable that accepts two arguments: a Request object and a RequestHandler object. Each middleware MUST return an instance of Psr\Http\Message\ResponseInterface.

    This example middleware is a Closure.

    Invokable class middleware example

    1. <?php
    2. use Psr\Http\Message\ServerRequestInterface as Request;
    3. use Psr\Http\Server\RequestHandlerInterface as RequestHandler;
    4. use Slim\Psr7\Response;
    6. class ExampleBeforeMiddleware
    7. {
    8.     /**
    9.      * Example middleware invokable class
    10.      *
    11.      * @param  ServerRequest  $request PSR-7 request
    12.      * @param  RequestHandler $handler PSR-15 request handler
    13.      *
    14.      * @return Response
    15.      */
    16.     public function __invoke(Request $request, RequestHandler $handler): Response
    17.     {
    18.         $response = $handler->handle($request);
    19.         $existingContent = (string) $response->getBody();
    21.         $response = new Response();
    22.         $response->getBody()->write('BEFORE' . $existingContent);
    24.     }
    25. }
    1. <?php
    3. use Psr\Http\Message\ServerRequestInterface as Request;
    4. use Psr\Http\Server\RequestHandlerInterface as RequestHandler;
    6. class ExampleAfterMiddleware
    7. {
    8.     /**
    9.      * Example middleware invokable class
    10.      *
    11.      * @param  ServerRequest  $request PSR-7 request
    12.      * @param  RequestHandler $handler PSR-15 request handler
    13.      *
    14.      * @return Response
    15.      */
    16.     public function __invoke(Request $request, RequestHandler $handler): Response
    17.     {
    18.         $response = $handler->handle($request);
    19.         $response->getBody()->write('AFTER');
    20.         return $response;
    21.     }
    22. }

    To use these classes as a middleware, you can use add(new ExampleMiddleware()); function chain after the $app route mapping methods get(), post(), put(), patch(), delete(), options(), any() or group(), which in the code below, any one of these, could represent $subject.

    1. <?php
    2. use Slim\Factory\AppFactory;
    4. require __DIR__ . '/../vendor/autoload.php';
    6. $app = AppFactory::create();
    8. // Add Middleware On App
    9. $app->add(new ExampleMiddleware());
    11. // Add Middleware On Route
    12. $app->get('/', function () { ... })->add(new ExampleMiddleware());
    14. $app->group('/', function () { ... })->add(new ExampleMiddleware());
    16. // ...
    18. $app->run();

    You may add middleware to a Slim application, to an individual Slim application route or to a route group. All scenarios accept the same middleware and implement the same middleware interface.

    Application middleware is invoked for every incoming HTTP request. Add application middleware with the Slim application instance’s add() method. This example adds the Closure middleware example above:

    This would output this HTTP response body:

    1. BEFORE Hello World AFTER

    Route middleware

    Route middleware is invoked only if its route matches the current HTTP request method and URI. Route middleware is specified immediately after you invoke any of the Slim application’s routing methods (e.g., get() or post()). Each routing method returns an instance of \Slim\Route, and this class provides the same middleware interface as the Slim application instance. Add middleware to a Route with the Route instance’s add() method. This example adds the Closure middleware example above:

    1. <?php
    2. use Psr\Http\Message\ResponseInterface as Response;
    3. use Psr\Http\Message\ServerRequestInterface as Request;
    4. use Psr\Http\Server\RequestHandlerInterface as RequestHandler;
    5. use Slim\Factory\AppFactory;
    7. require __DIR__ . '/../vendor/autoload.php';
    9. $app = AppFactory::create();
    11. $mw = function (Request $request, RequestHandler $handler) {
    12.     $response = $handler->handle($request);
    13.     $response->getBody()->write('World');
    15.     return $response;
    16. };
    18. $app->get('/', function (Request $request, Response $response, $args) {
    19.     $response->getBody()->write('Hello ');
    21.     return $response;
    22. })->add($mw);
    24. $app->run();

    This would output this HTTP response body:

    1. Hello World

    In addition to the overall application, and standard routes being able to accept middleware, the group() multi-route definition functionality, also allows individual routes internally. Route group middleware is invoked only if its route matches one of the defined HTTP request methods and URIs from the group. To add middleware within the callback, and entire-group middleware to be set by chaining add() after the group() method.

    When calling the /utils/date method, this would output a string similar to the below

    1. It is now 2015-07-06 03:11:01. Enjoy!

    Visiting /utils/time would output a string similar to the below

    1. It is now 1436148762. Enjoy!

    But visiting /(domain-root), would be expected to generate the following output as no middleware has been assigned

    Passing variables from middleware

    The easiest way to pass attributes from middleware is to use the request’sattributes.

    Setting the variable in the middleware:

    Getting the variable in the route callback:

    1. $foo = $request->getAttribute('foo');

    You may find a PSR-15 Middleware class already written that will satisfy your needs. Here are a few unofficial lists to search.