-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Run prepare hooks for parser errors #12890
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
Closed
koriyoshi2041
wants to merge
1
commit into
aio-libs:master
from
koriyoshi2041:fix-parser-error-prepare-hooks
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Allowed application-level ``on_response_prepare`` callbacks to run for parser-error responses so applications can adjust response headers such as ``Server`` consistently. |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this end up doing about the same thing as the old code? Seems like it's not going to solve the features requested..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the difference is where this lets the app request handler back in for the parser-error request.
For the default
AppRunnerpath,web_runner._make_request()seesmessage is ERRORand attachesrequest._match_info = MatchInfoError(HTTPBadRequest()). With this change,RequestHandler.start()builds that request first; when_match_infoexists, it uses the app-level request handler instead of the protocol_make_error_handlerfallback.Then
Application._handle()takes the existing system-route match info, builds middleware forSystemRoute, and returns theHTTPBadRequestresponse through the normal app path.finish_response()still callsresp.prepare(request), soon_response_preparefires. The fallback error handler remains for custom request factories that do not attach match info.I rechecked the targeted coverage locally:
Result:
2 passed, 1 skipped; the skipped one is the local checkout missing the C HTTP parser.