dongqin6926 2018-06-20 11:46
浏览 375
已采纳

laravel如何匹配路由优先级

Case 1: web.php:

Route::get('foo/{id}', function () {
    return 'Route 1';
});
Route::get('foo/bar', function () {
    return 'Route 2';
});
Route::get('foo/bar', function () {
    return 'Route 3';
});

When I browse to localhost/foo/bar I got Route 1 which correct since the url match the first route.

Case 2: web.php:

Route::post('foo/{id}', function () {
    return 'Route 1';
});
Route::get('foo/bar', function () {
    return 'Route 2';
});
Route::get('foo/bar', function () {
    return 'Route 3';
});

When I browse to localhost/foo/bar I got Route 3.

My question is why i got Route 3 intead of Route 2. Isn't logical to get Route 2 since the url match the second route first?! Why does Laravel continue to match the routes after match is found (route 2 in my case)?

  • 写回答

2条回答 默认 最新

  • douzhuoxia0587 2018-06-20 12:06
    关注

    The second foo/bar route overrides the first, because the HTTP Method and URI are the same.

    The HTTP Method + URI combo acts as a primary key for a route. The combination of the two have to be unique - you can't have two different destinations for the same route.

    So, Laravel takes a "last in, first out" approach, where any previous definition (e.g. "Route 2") is overwritten. You can confirm this by running php artisan route:list in the command line to see what route definitions Laravel will actually attempt to match.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论
查看更多回答(1条)
编辑
预览

报告相同问题?

手机看
程序员都在用的中文IT技术交流社区

程序员都在用的中文IT技术交流社区

专业的中文 IT 技术社区,与千万技术人共成长

专业的中文 IT 技术社区,与千万技术人共成长

关注【CSDN】视频号,行业资讯、技术分享精彩不断,直播好礼送不停!

关注【CSDN】视频号,行业资讯、技术分享精彩不断,直播好礼送不停!

客服 返回
顶部