-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A non-matching METHOD is 'METHOD_NOT_ALLOWED' on static routes #50
Comments
Yeah, |
nikic
added a commit
that referenced
this issue
May 15, 2015
If the static route doesn't exist for the given method, try matching against dynamic ones as well. Allowed methods are now collected from both static and dynamic routes. This changes the route data format, so cache is no longer valid -- maybe include a version identifier in the cache file?
Should be fixed now. |
Thanks for the fast response! <-see what I did there? |
how can we show the actual controller name |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In this example performing the request 'GET /users.json' the static route /users.json matches the request and returns METHOD_NOT_ALLOWED. Shouldn't the GET /{entity}.json route match the request?
The text was updated successfully, but these errors were encountered: