Resolve KeyError exception when calling unsupported request method #298
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.
What do these changes do?
When using a web.View class, and querying with an unsupported request method (e.g: class implements GET, client queries with POST), the client would receive an "Empty Reply" from the server, and the server would log a KeyError exception.
This patch resolves the issue, and permits the partially prepared 405 response through to the client.
I'm not sure if this abides by the CORS rules, but it's certainly better than an exception and no response.
Are there changes in behavior for the user?
No changes required.
Related issue number
KeyError
and "Empty Reply" are still present.Checklist
Documentation reflects the changes(N/A)CHANGES
folderTests
I'm not sure how to go about testing this fix, but I have provided a demo application and
curl
comamnd to demonstrate it below.