In Laravel, duplicate code can be reduced through global middleware and middleware groups. Global middleware is suitable for all requests, such as setting time zones and loading language packs. The registration method is to add class names to the $middleware array of app/Http/Kernel.php, but time-consuming operations should be avoided; middleware groups are used to apply multiple middleware to a set of routes on demand, such as web and API groups. They can be customized and applied to routes, such as authentication and permission judgment middleware to form an admin group, and applied through Route::middleware('admin'); global middleware is selected for system-level operations, and middleware groups are used for business division, thereby improving project structure clarity and maintainability.
In Laravel, if you want some middleware to take effect on all routes or groups of routes instead of adding them to each route one by one, you can use a global middleware or middleware group. This method can reduce duplicate code and improve maintainability.

Global Middleware: Applicable to all requests
The global middleware will be executed in every request . Common uses include loading language packs at startup, setting default time zones, etc.

To register a global middleware:
- Open
app/Http/Kernel.php
- Add your middleware class name in the
$middleware
array
For example:

protected $middleware = [ \App\Http\Middleware\TrustHosts::class, \App\Http\Middleware\TrustProxies::class, \Fruitcake\Cors\HandleCors::class, \App\Http\Middleware\PreventRequestsDuringMaintenance::class, \Illuminate\Foundation\Http\Middleware\ValidatePostSize::class, \App\Http\Middleware\TrimStrings::class, \Illuminate\Foundation\Http\Middleware\ConvertEmptyStringsToNull::class, \App\Http\Middleware\LoadLanguage::class, // New global middleware];
Note: Global middleware will affect all requests, so don't put too much time-consuming operations in it, such as database query. Unless you do need it to work on all requests, it is recommended to use middleware groups to be more flexible.
Middleware group: applied on demand to common routing collections
Middleware groups are suitable for middleware combinations that you want to apply to multiple routes together. The most common examples are web
and api
groups.
To create or modify a middleware group:
- Open
app/Http/Kernel.php
- Find
$middlewareGroups
array - Add or edit a list of middleware in a group
For example, if you want to add permission verification middleware to the background management page:
'admin' => [ \App\Http\Middleware\Authenticate::class, \App\Http\Middleware\CheckAdminRole::class, \Illuminate\Routing\Middleware\SubstituteBindings::class, ],
Then, when defining the route, use it like this:
Route::middleware('admin')->prefix('admin')->group(function () { Route::get('/dashboard', [AdminController::class, 'dashboard']); Route::resource('users', UserController::class); });
The advantage of this is that it has clear structure and is convenient for unified management. At the same time, it can also avoid writing a bunch of middleware on each route, reducing errors and maintenance costs.
How to choose a global or middleware group?
- Use global middleware : suitable for system-level operations, such as basic security restrictions, logging, initialization configuration, etc.
- Middleware group : suitable for business scenario division, such as web foreground, API interface, backend management, etc.
To give a practical example:
- You have a mall project, and the front-end user access requires session support, and the back-end administrator also needs additional authentication.
- Then you can place
\App\Http\Middleware\EncryptCookies::class
,\Illuminate\Session\Middleware\StartSession::class
, etc. inweb
group. - The background interface uses a custom
admin
group, which contains middleware for authentication permission judgment.
Basically that's it. Rational use of global and middleware groups can make your Laravel project structure clearer and easier to expand and maintain.
The above is the detailed content of Applying Global or Group Middleware in Laravel. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

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

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

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

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.

LaravelSanctum is suitable for simple, lightweight API certifications such as SPA or mobile applications, while Passport is suitable for scenarios where full OAuth2 functionality is required. 1. Sanctum provides token-based authentication, suitable for first-party clients; 2. Passport supports complex processes such as authorization codes and client credentials, suitable for third-party developers to access; 3. Sanctum installation and configuration are simpler and maintenance costs are low; 4. Passport functions are comprehensive but configuration is complex, suitable for platforms that require fine permission control. When selecting, you should determine whether the OAuth2 feature is required based on the project requirements.

Laravel simplifies database transaction processing with built-in support. 1. Use the DB::transaction() method to automatically commit or rollback operations to ensure data integrity; 2. Support nested transactions and implement them through savepoints, but it is usually recommended to use a single transaction wrapper to avoid complexity; 3. Provide manual control methods such as beginTransaction(), commit() and rollBack(), suitable for scenarios that require more flexible processing; 4. Best practices include keeping transactions short, only using them when necessary, testing failures, and recording rollback information. Rationally choosing transaction management methods can help improve application reliability and performance.

The core of handling HTTP requests and responses in Laravel is to master the acquisition of request data, response return and file upload. 1. When receiving request data, you can inject the Request instance through type prompts and use input() or magic methods to obtain fields, and combine validate() or form request classes for verification; 2. Return response supports strings, views, JSON, responses with status codes and headers and redirect operations; 3. When processing file uploads, you need to use the file() method and store() to store files. Before uploading, you should verify the file type and size, and the storage path can be saved to the database.
