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.
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
fix: when disconnecting, close the underlying connection before the response InputStream #1315
fix: when disconnecting, close the underlying connection before the response InputStream #1315
Changes from 2 commits
61487b5
0f3689a
522041f
90ff804
0849b3d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Why do you need to call this at all? I'd think disconnecting alone is enough.
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'm not sure of the original intention for sure, but it looks like it's supposed to close the response's
InputStream
so you can't read from it anymore - a way of letting google-http-client cleaning up the connections and their resources. This class was designed beforeAutoClosable
was available (and possibly even beforeClosable
was available).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.
The more I look at this, the more off this seems. I think what we should do is:
ignore()
actually reads and decodes the bytes remaining on the stream. That could be quite a long-running operation. The point of disconnecting is to throw those away and not waste time reading them.If you see otherwise, let's discuss.
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.
That seems reasonable, I'll try it out.
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 modified
ignore()
to directly close theLowLevelHttpResponse
'sInputStream
rather than doing the extra reading logic ingetContent()
.I still do need to swap the
disconnect()
andignore()
lines as theApacheHttpResponse
will still try to read the content from its input stream unless it's disconnected first.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'm not sold this is the best solution -- the tests do pass however.
An alternative is to mark that this response is "disconnecting" and in
getContent()
don't read from the underlying response if we're "disconnecting".