Cleanup properly after hijacking a request #164
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
The logging handler hijacks the HTTP request, but does not properly clean up the files left behind by multipart forms. The HTTP library normally does this, but if the connection is hijacked, all responsibility to clean up is on the hijacker.
mmussomele
force-pushed
the
hijack-cleanup
branch
from
21f9588
to
428858a
Compare
|
Great catch - thanks @mmussomele |
elithrar
approved these changes
Jul 20, 2019
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.
The logging handler hijacks the HTTP request, but does
not properly clean up the files left behind by multipart
forms.
The HTTP library normally does this, but if the connection is hijacked,
all responsibility to clean up is on the hijacker.
Summary of Changes