Middleware adds additional layers to your Webiik application as you can see on the picture below. It can be useful when you have code that needs to be executed by every request or by more route specific requests.
Each middleware is executed and can continue to the next one until it reaches a route controller. Route controller itself is also the middleware. Application middleware layers are executed at first, then are executed route specific middleware layers. Route controller is executed at last.
Store your middleware classes in folder
private/code/middleware and use namespace
namespace Webiik\Middleware. Read Middleware documentation to learn more about writing middleware.
You have written your middleware, now it’s time to add it to your Webiik application.
string $controller => array $data,
'Webiik\Middleware\Core\SetSecurityHeaders:run' => ,
Webiik adds middleware using the method add(string $controller, $data = ): void.
🌐 Webiik supports language related middleware registration files, for example:
middleware.en.php. Webiik always loads only one
middleware registration file with the following priority: *.en.php, *.php.
ℹ️ To add route specific middleware, read Routing.
If you use any configuration values inside your middleware, it can be a good idea to place these values into a separate file. The separate configuration file allows you to configure your middleware according to the environment and/or language.
'MiddlewareClassName' => [ 'customKeyName' => 'customValue', ],
Key name can be custom. However, it’s a good idea to set a key name similar to associated middleware class name, middleware method or parameter.
👨💻🌐 Webiik supports local and language related middleware configuration. For example:
resources.en.local.php. Webiik always loads only one service configuration file with the following priority:
*.php. Never publish your local configuration file to production. If you deploy your Webiik project using the Git, Webiik ignores local configuration files, so you don’t have to take care.