Zlib / incorrect header check in vanilla request
See original GitHub issueMy request looks like this:
var req = request
.get("https://apis.live.net/v5.0/me/contacts")
.query({
"access_token": accessToken
}).end(function() { });
Seems to be enough to give this error:
Error: incorrect header check
at Zlib._binding.onerror (zlib.js:295:17)
When I build the URL myself with a valid access token and point my browser to it, the request succeeds.
Issue Analytics
- State:
- Created 10 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Incorrect Header Check when using zlib in node.js
1) Collect all the buffers in an array, and in the end event concatentate them using Buffer.concat() . Then call gunzip on the...
Read more >'incorrect header check' parsing gzip response on every call ...
I am seeing the following error on every request but the first to a resource ... Zlib / incorrect header check in vanilla...
Read more >Post by alfsaturn in RPA Extract comments - itch.io
File "encodings\zlib_codec.py", line 43, in zlib_decode zlib.error: Error -3 while decompressing data: incorrect header check [8376] Failed to execute ...
Read more >3 while decompressing: incorrect header check - zlib.error
PYTHON : zlib.error: Error -3 while decompressing: incorrect header check [ Gift : Animated Search Engine ...
Read more >zlib.gunzip() on file contents returns Error: incorrect header ...
zlib.error: Error -3 while decompressing: incorrect header check ... zlib.decompress(deflate_data) Traceback (most recent call last): File "<stdin>", ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@defunctzombie i’m still seeing this. newer versions of what? superagent, zlib?
In browser response headers indicate encoding is
deflate
. When I add this to my request:Request succeeds. So problem seems to be in unencoding deflate-encoded streams. (I guess.)