Remove Content-Encoding header when we auto unzip the response steram #359
Conversation
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
|
By analyzing the blame information on this pull request, we identified @grantland and @wangmengyan95 to be potential reviewers. |
|
LGTM |
wangmengyan95
added a commit
that referenced
this pull request
Jan 21, 2016
…_encoding_header_when_auto_unzip_response Remove Content-Encoding header when we auto unzip the response steram
wangmengyan95
deleted the
wangmengyan.remove_content_encoding_header_when_auto_unzip_response
branch
|
@wangmengyan95 updated the pull request. |
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.
Fixes #355
When we use
ParseApacheHttpClient, after we unzip the response stream, we should also remove theContent-Encodingheader.