Decompress slightly invalid gzip response

[gregory90]

Prevents following error when compressed response is slightly invalid/truncated (it happens rarely, but still)

Error: unexpected end of file
  File "zlib.js", line 370, col 17, in Zlib._handle.onerror

[codecov-io]

Codecov Report

Merging #239 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #239      +/-   ##
==========================================
+ Coverage   98.97%   98.97%   +<.01%     
==========================================
  Files           6        6              
  Lines         391      392       +1     
  Branches      117      117              
==========================================
+ Hits          387      388       +1     
  Misses          2        2              
  Partials        2        2

Impacted Files	Coverage Δ
src/index.js	97.33% <100%> (+0.03%)	✅

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 673ebb2...86d834e. Read the comment docs.

[bitinn]

Note, the original handling of raw inflate response is a hack for older Microsoft IIS/Apache servers, not required by spec, and not for specific websites (I waited a longtime before adding the hack). I want to know which old servers would intentionally send broken gzip? If it's pretty widespread we would consider it. Otherwise we think the site owner is better off fixing them. (From my phone)

…

在 2017年2月22日，16:26，gregory90 ***@***.***> 写道： Prevents following error when compressed response is slightly invalid/truncated (it happens rarely, but still) Error: unexpected end of file File "zlib.js", line 370, col 17, in Zlib._handle.onerror You can view, comment on, or merge this pull request online at: #239 Commit Summary decompress slightly invalid gzip File Changes M src/index.js (15) M test/server.js (10) M test/test.js (11) Patch Links: https://github.com/bitinn/node-fetch/pull/239.patch https://github.com/bitinn/node-fetch/pull/239.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[gregory90]

Some reference:
nodejs/node#8701
request/request#2492

I'm seeing these errors sometimes, and did get to issues mentioned above. node-fetch doesn't have this implemented. If that's not what you want, don't hesitate to close this PR, but many clients are using this approach. I'm not an expert by any means though:)

[TimothyGu]

Merged in a1e76b9. Thanks!