Incorrect header check
See original GitHub issueBasic info:
-
**Node.js version:V8
-
**jsdom version:11
let optionss = { includeNodeLocations: true, runScripts: "dangerously", resources: "usable", userAgent: "newsBot", virtualConsole };
JSDOM.fromURL("http://www.tribuneindia.com/news/haryana/10-named-for-violence-ahead-of-saini-s-event/468169.html", optionss) .then(dom => { console.log(dom.serialize()) })
This is throwing incorrect header check at Inflate.zlibOnError (zlib.js:146:15) errno: -3, code: ‘Z_DATA_ERROR’
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
zlib.error: Error -3 while decompressing: incorrect header check
You have this error: zlib.error: Error -3 while decompressing: incorrect header check. Which is most likely because you are trying to check headers...
Read more >incorrect header check · Issue #2406 · axios/axios - GitHub
Hello, why this code is throwing "incorrect header check"? ... I tested in the browser (even in incognito mode) and is returning an...
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 >[CAS 6.1] Base64 decoding failed / incorrect header check
We have recently upgraded from CAS 5.2.x to CAS 6.1.x - everything appears to be working as expected, however we are seeing the...
Read more >Incorrect header check - Questions - Kong Nation
I'm trying to send request throw postman and I'm getting the error incorrect header check, but if I send curl request I get...
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 Free
Top 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
It’s not really clear to me what the issue is, but from @TimothyGu’s comment it sounds like it’s probably https://github.com/whatwg/fetch/issues/716, which is basically in need of a lot of tests in order to make progress.
do we know which jsdom/requests/etc versions are the proper ones to use going forward to not get this issue?