You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MethodNotAllowedException is thrown depending on the list of HTTP Methods from all the routes bound to the Router instead of being based on URL.
This leads to the following cases when it seems like the router doesn't work as intended:
On requesting a nonexistent route (path) one can get MethodNotAllowedException being throwpn (instead of RouteNotFoundException) if the requesting method is not found at any of registered routes.
On requesting a registered route (path) using the method that is not supported by that route one can get no exception being thrown if that method is present anywhere else.
You can also check RFC to make sure that the current behavior is improper.
The text was updated successfully, but these errors were encountered:
According to the following code in
Router::match
MethodNotAllowedException
is thrown depending on the list of HTTP Methods from all the routes bound to the Router instead of being based on URL.This leads to the following cases when it seems like the router doesn't work as intended:
MethodNotAllowedException
being throwpn (instead ofRouteNotFoundException
) if the requesting method is not found at any of registered routes.You can also check RFC to make sure that the current behavior is improper.
The text was updated successfully, but these errors were encountered: