Method Not Allowed error message may display incorrect route path

[IM-Jehong-Ahn]

Current Behavior

Currently, AbstractRouteCollection::checkForAlternateVerbs() checks for matching routes across all HTTP methods except the requested one. During this process, routes with wildcard patterns like {any} can also be matched.

Issue

For example:

Route::get('/users/{id}', 'UserController@show');
Route::post('{any}', 'CatchAllController@handle')->where('any', '.');

When a user sends a PUT request to /users/123, the current implementation finds the {any} route and suggests "The PUT method is not supported for route /users/123. Supported methods: POST." - which could be misleading because the POST method actually points to a different catch-all route, not the specific /users/{id} endpoint.

Proposed Solution

1. Modify checkForAlternateVerbs() to only return routes that exactly match the current path
2. Include the actual matched route path in the error message