在Laravel 中，路由是應(yīng)用程序的入口點(diǎn)，用於定義客戶端請(qǐng)求特定URI 時(shí)的響應(yīng)邏輯。路由將URL 映射到對(duì)應(yīng)的處理代碼，通常包含HTTP 方法、URI 和動(dòng)作（閉包或控制器方法）。 1. 路由定義基本結(jié)構(gòu)：使用Route::verb('/uri', action) 的方式綁定請(qǐng)求；2. 支持多種HTTP 動(dòng)詞如GET、POST、PUT 等；3. 可通過{param} 定義動(dòng)態(tài)參數(shù)並傳遞數(shù)據(jù)；4. 路由可命名以便生成URL 或重定向；5. 使用分組功能統(tǒng)一添加前綴、中間件等共享設(shè)置；6. 路由文件按用途分為web.php、api.php、console.php 和channels.php，分別對(duì)應(yīng)不同場(chǎng)景。

In Laravel, routes are essentially the entry points to your application — they define how your app responds to a client request at a specific URI. Think of them as the mapping between URLs and the code that handles them.

Basic Concept: What Are Routes?

At their core, routes in Laravel determine what happens when someone visits a certain URL on your site. For example, if you have a blog, visiting /posts might show a list of posts, while /posts/1 shows a specific one. Each of these URLs is tied to a route that tells Laravel where to go and what to do.

You define routes in files inside the routes directory. The most common ones are:

• web.php – for regular HTML pages (with session state, CSRF protection, etc.)
• api.php – for stateless APIs
• console.php – for Artisan commands
• channels.php – for broadcast channels

Each route typically includes an HTTP verb (like GET or POST), a URI, and an action (a controller method or closure).

Defining Simple Routes

The simplest way to define a route is using a closure directly in your route file. Here's an example from routes/web.php :

 Route::get('/hello', function () {
    return 'Hello, Laravel!';
});

This means when someone accesses /hello via a GET request, Laravel will return "Hello, Laravel!".

You can also use controller methods instead of closures, which keeps your route files clean and separates concerns:

 Route::get('/posts', [PostController::class, 'index']);

Here, accessing /posts will call the index method of PostController .

Some other common HTTP verbs include:

• Route::post() – for form submissions
• Route::put() – for updates
• Route::delete() – for deletions
• Route::patch() – partial updates

Route Parameters: Passing Data Through URLs

If you need to pass dynamic data through a URL (like a user ID or post slug), Laravel makes it easy with route parameters.

For example:

 Route::get('/user/{id}', function ($id) {
    return 'User ID: ' . $id;
});

Now, visiting /user/123 would display "User ID: 123".

You can have multiple parameters too:

 Route::get('/post/{year}/{slug}', function ($year, $slug) {
    return "Post from $year: $slug";
});

These parameters can also be optional by giving them a default value:

 Route::get('/page/{number?}', function ($number = 1) {
    return "Page number: $number";
});

Naming and Grouping Routes

As your app grows, naming routes becomes super useful — especially when generating URLs or redirects.

 Route::get('/about', function () {
    return view('about');
})->name('about.page');

Then later, you can reference it like this:

 route('about.page');

Grouping routes helps organize shared logic, such as middleware or prefixes:

 Route::prefix('admin')->group(function () {
    Route::get('/dashboard', function () {
        return 'Admin Dashboard';
    })->name('admin.dashboard');

    Route::get('/users', function () {
        return 'Admin Users';
    })->name('admin.users');
});

This way, all routes under the group have /admin prepended automatically.

Middleware can also be applied to a group:

 Route::middleware(['auth'])->group(function () {
    Route::get('/profile', function () {
        return 'Your Profile';
    });
});

This ensures only authenticated users can access those routes.

That's the general idea of?? how routing works in Laravel. It gives you a lot of flexibility without being overly complex once you get the hang of it.

以上是Laravel中的路線是什麼？如何定義？的詳細(xì)內(nèi)容。更多資訊請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！