fix: handle methodnotallowed with path variables #512
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, any route with a pathvariable will return a 404 on a method not allowed condition when it should return a 405. This adds the necessary bool setting to the route context for the path variable case.
|
thanks for the report + fix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, any route with a pathvariable will return a 404 on a method not allowed condition when it should return a 405. This adds the necessary bool setting to the route context for the path variable case.
We noticed this when we upgraded from v4.0.1 to v4.1.1. A little git bisect magic later, and it turned out to be in some of the regex additions. Repeating the setting of the rctx.methodNotAllowed boolean looked like the most straightforward approach.