fix(http): handle response decompression properly #1563
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
|
|
luneo7
changed the title
|
/cc @hassy |
douglasmelo
approved these changes
Aug 4, 2022
wcaquino
approved these changes
Aug 4, 2022
|
nice one @luneo7, thanks for your PR! |
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.
Almost the same thing as #999
Since we are using
decompressResponseandon('data')is added to it,on('end')should also be executed on the decompressResponse... but it is being executed on raw response causing a race condition, so when response end happens, response data didn't happen yet, and we end up with empty body string.This PR makes the handle response use decompressResponse for everything instead of mixing raw response object and the decompress response object.
Fixes #1562