You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While talking to a web server on an embedded device, asking for gzip content encoding I get responses that are considered OK by all major browsers (Chrome, Firefox, IE) and also cURL. However, the Node zlibmodule considers the gzip stream incomplete and throws an error. The error returned by the zlib module reads: Error: unexpected end of file at Zlib._handle.onerror (zlib.js:363:17). Inspecting the gzip response it seems to be missing a footer detailing the CRC and the length of the compressed data.
A small program that reproduces this with an actual response from the device in it:
Activity
jhamhader commentedon Mar 17, 2016
This behavior was added in #2595. You can see the answer to a similar issue, #4030.
evanlucas commentedon Mar 17, 2016
@peterkooijmans does this same issue occur on node v5.8.0?
peterkooijmans commentedon Mar 18, 2016
@evanlucas node v5.8.0 has the exact same behavior.
Fishrock123 commentedon Mar 18, 2016
Looks like it has been this was since v5. @peterkooijmans could you take a look at #4030 for a potential solution?
zlib: Make the finish flush flag configurable
zlib: Make the finish flush flag configurable
zlib: Make the finish flush flag configurable
zlib: Make the finish flush flag configurable
zlib: Make the finish flush flag configurable