全局中間件是Laravel中針對每個HTTP請求運行的代碼，其作用於所有請求，不局限於特定路由或組。它們通常用於處理如CORS頭、維護模式檢查、輸入標準化等任務。常見內(nèi)置全局中間件包括HandleCors、TrustHosts、PreventRequestsDuringMaintenance、ValidatePostSize及TrimStrings等，這些類定義在app/Http/Middleware目錄，並通過App\Http\Kernel中的$middleware屬性註冊。要添加自定義全局中間件，可使用php artisan make:middleware命令創(chuàng)建中間件類，在handle()方法中編寫邏輯，並將其加入$middleware數(shù)組，無需通過路由或控制器註冊。但需注意，全局中間件會影響所有類型的請求（如API、靜態(tài)資源），若僅需應用於特定場景，應考慮使用中間件組；同時，性能敏感操作如數(shù)據(jù)庫調(diào)用應謹慎使用，避免影響整體性能。總之，全局中間件適合處理跨切面任務，但需合理使用以避免副作用。

Global middleware in Laravel are pieces of code that run on every single HTTP request that comes into your application. They sit at the global level, meaning they're not tied to any specific route or group — they apply universally.

Unlike route-specific middleware (like ones that check for authentication or user roles), global middleware affect everything. The most common examples are things like starting a session, checking maintenance mode, or handling CORS headers. These are background tasks you want to happen no matter which page someone is hitting.

Common Global Middleware in Laravel

Laravel ships with several middleware out of the box that are typically registered globally. These include:

• HandleCors : Handles Cross-Origin Resource Sharing (CORS) headers.
• TrustHosts , TrustProxies : Deal with secure connections and reverse proxies.
• PreventRequestsDuringMaintenance : Blocks access when the app is in maintenance mode.
• ValidatePostSize : Checks if incoming POST requests are within allowed size limits.
• TrimStrings , ConvertEmptyStringsToNull : Handle input normalization.

These are all middleware classes that live in the app/Http/Middleware directory and are applied automatically via the global() method inside the App\Http\Kernel class.

How to Add Custom Global Middleware

If you have logic you want to run on every request — like logging IP addresses, setting timezone based on user location, or custom rate limiting — you can create your own middleware and register it globally.

Here's how:

1. Run php artisan make:middleware YourMiddlewareName
2. Write your logic inside the handle() method
3. Add the middleware class to the $middleware property in App\Http\Kernel

You don't need to use Route::middleware() or assign them in controller constructors — just placing them in the global list makes them active everywhere.

For example, if you wanted to log every incoming request before anything else happens, you could write a simple logger middleware and register it at the top of the $middleware array.

When Not to Use Global Middleware

Just because something runs on every request doesn't always mean it should. Global middleware runs for every HTTP request — including API calls, asset requests, and AJAX endpoints. If your logic only needs to run on web pages or authenticated routes, consider using middleware groups ( web , api ) instead.

Also, be careful with performance. A slow global middleware will impact every single endpoint in your app. So, if you're making database calls or external API requests inside global middleware, make sure they're optimized and not blocking unnecessarily.

Final Note

Global middleware are powerful but easy to overlook — they quietly do their job behind the scenes. You don't usually notice them until something goes wrong (like a missing CORS header or an incorrectly trusted proxy). Once you understand how they fit into the overall request lifecycle, they become a solid tool for handling cross-cutting concerns in your Laravel apps.

基本上就這些。

以上是Laravel的全球中間件是什麼？的詳細內(nèi)容。更多資訊請關注PHP中文網(wǎng)其他相關文章！