fix: invalid content type recognised as request body error #844
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
slonka
force-pushed
the
content-type-error-incorrectly-recognised-as-request-body-error
branch
from
ec4c55a to
a0fb795
Compare
…correctly as request body error
slonka
force-pushed
the
content-type-error-incorrectly-recognised-as-request-body-error
branch
from
a0fb795 to
ce49eaf
Compare
|
Closing as this isn't a bug. |
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.
work in progress, just to better explain the issue 843
add test case to show that invalid content type is recognised incorrectly as request body error
closes #843