Middleware provides a convenient mechanism for inspecting and filtering HTTP requests entering your application. For example, Lithe includes middleware that checks if the user is authenticated. If not, the middleware will redirect the user to the login screen. If the user is authenticated, the middleware allows the request to proceed.
How Middleware Works in Lithe
In Lithe, middleware are functions with access to the request object ($req), response object ($res), and the $next function in the application's request-response cycle. The $next function, when invoked, calls the next middleware in the current stack.
Middleware functions provide a convenient way to inspect, filter, and manipulate incoming HTTP requests to your application. They can:
- Execute any code.
- Modify the request and response objects.
- End the request-response cycle.
- Call the next middleware in the stack.
If the current middleware doesn't terminate the request-response cycle, it must call $next() to pass control to the next middleware. Otherwise, the request will remain pending.
Elements of a Middleware Function
The following code demonstrates the elements of a middleware function:
$app->use(function ($req, $res, $next) { $next(); });
Where:
- $req: HTTP request argument, conventionally called $req.
- $res: HTTP response argument, conventionally called $res.
- $next: Callback argument, conventionally called $next.
Defining Middleware
Here’s a simple example of middleware called myLogger. This middleware prints the message LOGGED every time a request passes through it. It’s defined as a function assigned to a variable called myLogger:
$myLogger = function ($req, $res, $next) { echo 'LOGGED'; $next(); };
Notice the $next() call above. This function calls the next middleware in the application. $next() isn't a built-in PHP or Lithe function but is the third argument passed to the middleware function. Though $next() could be named anything, by convention, it is always called "next." To avoid confusion, stick to this convention.
Imagine middleware as a series of "layers" that HTTP requests pass through before reaching your application. Each layer can examine or reject the request.
Loading Middleware
To load middleware, you call the use() method of the LitheApp class, specifying the middleware function. For example:
$app = new \Lithe\App; $myLogger = function ($req, $res, $next) { echo 'LOGGED'; $next(); }; $app->use($myLogger); $app->get('/', function ($req, $res, $next) { $res->send('Hello World!'); });
Whenever the app receives a request, the message "LOGGED" will be printed. The order of middleware loading matters: those loaded first are executed first.
The myLogger middleware simply prints a message, then passes the request to the next middleware using $next().
Using Middleware
A Lithe application can use the following types of middleware:
- Application-level Middleware
- Router-level Middleware
- Third-party Middleware
Application-level Middleware
You attach application-level middleware to an instance of the application using the use() or METHOD() methods, where METHOD refers to the HTTP method (e.g., GET, PUT, POST) in lowercase.
This example shows middleware without a path. The middleware runs every time a request is received:
$app->use(function ($req, $res, $next) { $next(); });
In the example below, middleware handles a GET request to the path /user/:id:
$myLogger = function ($req, $res, $next) { echo 'LOGGED'; $next(); };
Router-level Middleware
Router-level middleware works like application-level middleware but is attached to an instance of LitheHttpRouter:
$app = new \Lithe\App; $myLogger = function ($req, $res, $next) { echo 'LOGGED'; $next(); }; $app->use($myLogger); $app->get('/', function ($req, $res, $next) { $res->send('Hello World!'); });
You load router-level middleware using the use() and METHOD() functions.
Here’s an example of router-level middleware:
$app->use(function ($req, $res, $next) { echo 'Hello World!'; $next(); });
Third-party Middleware
You can use third-party middleware to add functionality to your Lithe applications. Install the required PHP module and then load it at the application or router level.
Here’s an example of loading session middleware with LitheMiddlewareSessionsession:
$app->get('/user/:id', function ($req, $res, $next) { if ($req->param('id') === '0') { return $next(); } $res->send('ID is not 0'); }, function ($req, $res) { $res->send('regular'); });
For a list of third-party middleware commonly used with Lithe, check the Third-party Middleware resource.
Configurable Middleware
If you need your middleware to be configurable, you can create a function that accepts an array of options or other parameters and then returns the middleware implementation based on those parameters. See the example below:
$router = new \Lithe\Http\Router;
Now, you can use the middleware with custom configurations:
$router = new \Lithe\Http\Router; $router->use(function ($req, $res, $next) { echo 'Time: ', Date('H:i:s'), '<br>'; $next(); }); $router->get('/user/:id', function ($req, $res, $next) { if ($req->param('id') === '0') { $res->redirect('/'); } $next(); }, function ($req, $res) { echo $req->param('id'); $res->render('special'); }); $app->use('/api', $router);
To create middleware that other developers can install via Composer, there is a package called lithemod/flow. It provides interfaces and utilities for handling HTTP requests and responses in Lithe, which facilitates the creation of standardized and ready-to-use middlewares across various applications.
lithemod/flow helps build robust middlewares by providing a unified interface for Request and Response, making development more efficient and organized. This simplifies the integration of your middleware into other projects and ensures that the code follows consistent standards.
The above is the detailed content of Middleware in Lithe: How It Works and How to Create Your Own. For more information, please follow other related articles on the PHP Chinese website!

ThesecrettokeepingaPHP-poweredwebsiterunningsmoothlyunderheavyloadinvolvesseveralkeystrategies:1)ImplementopcodecachingwithOPcachetoreducescriptexecutiontime,2)UsedatabasequerycachingwithRedistolessendatabaseload,3)LeverageCDNslikeCloudflareforservin

You should care about DependencyInjection(DI) because it makes your code clearer and easier to maintain. 1) DI makes it more modular by decoupling classes, 2) improves the convenience of testing and code flexibility, 3) Use DI containers to manage complex dependencies, but pay attention to performance impact and circular dependencies, 4) The best practice is to rely on abstract interfaces to achieve loose coupling.

Yes,optimizingaPHPapplicationispossibleandessential.1)ImplementcachingusingAPCutoreducedatabaseload.2)Optimizedatabaseswithindexing,efficientqueries,andconnectionpooling.3)Enhancecodewithbuilt-infunctions,avoidingglobalvariables,andusingopcodecaching

ThekeystrategiestosignificantlyboostPHPapplicationperformanceare:1)UseopcodecachinglikeOPcachetoreduceexecutiontime,2)Optimizedatabaseinteractionswithpreparedstatementsandproperindexing,3)ConfigurewebserverslikeNginxwithPHP-FPMforbetterperformance,4)

APHPDependencyInjectionContainerisatoolthatmanagesclassdependencies,enhancingcodemodularity,testability,andmaintainability.Itactsasacentralhubforcreatingandinjectingdependencies,thusreducingtightcouplingandeasingunittesting.

Select DependencyInjection (DI) for large applications, ServiceLocator is suitable for small projects or prototypes. 1) DI improves the testability and modularity of the code through constructor injection. 2) ServiceLocator obtains services through center registration, which is convenient but may lead to an increase in code coupling.

PHPapplicationscanbeoptimizedforspeedandefficiencyby:1)enablingopcacheinphp.ini,2)usingpreparedstatementswithPDOfordatabasequeries,3)replacingloopswitharray_filterandarray_mapfordataprocessing,4)configuringNginxasareverseproxy,5)implementingcachingwi

PHPemailvalidationinvolvesthreesteps:1)Formatvalidationusingregularexpressionstochecktheemailformat;2)DNSvalidationtoensurethedomainhasavalidMXrecord;3)SMTPvalidation,themostthoroughmethod,whichchecksifthemailboxexistsbyconnectingtotheSMTPserver.Impl


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

SublimeText3 Chinese version
Chinese version, very easy to use

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Zend Studio 13.0.1
Powerful PHP integrated development environment

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool
