openapi3filter: Reject requests with body when non expected (issue 1100) #1101
Conversation
This file contains hidden or 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
CynanX
force-pushed
the
master
branch
3 times, most recently
from
70fbd7b to
08e38e5
Compare
CynanX
changed the title
|
@fenollp Hi. I believe this solves issue 1100. I'm not sure of the protocol to get this reviewed? I couldn't see a contributing guide so forgive me if I've not done this correctly. Thank you for you time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When a the specification does not specify a request body but one is included the validation currently passes.
This change will reject the request.
An example use case is when validating a DELETE request where you do not expect a body.