GitLab

If a response is not complete and has a content-encoding header, it
should not be marked as truncated since we do not want it to lead to
range requests for future requests.

TEST=net_unittests --gtest_filter=
WritersTest.ContentEncodingShouldNotTruncate

Also manually verified that the test case reported in the bug is fixed.

Bug: 820862
Change-Id: Ie3f4098e769e257632058af2215054809ca8c89f
Reviewed-on: https://chromium-review.googlesource.com/962346
Commit-Queue: Shivani Sharma <shivanisha@chromium.org>
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543481}