-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid signature: 0x8080014 when piping from HTTP #73
Comments
+1 |
Have the same issue on Mac. Strange thing is that if I write http response to the zip file on disk and then process it from file it works.
|
Same here @pbochynski |
+1 :( |
Bad news: This repo appears to be abandoned. It comes down to the lines in
should be
|
Thank you @dvalentiate |
Same here @pbochynski |
Thanks you as well!! |
Thank you @dvalentiate for the tip. Swichting to |
Thank you @dvalentiate for the tip. Swichting to unzip2 fixed it for me: 👬 |
EvanOxfeld/node-unzip#73 2017-07-09T20:19:31.408545+00:00 app[web.1]: 1499631571408 - Origin: Worker (PID 35) 2017-07-09T20:19:31.408547+00:00 app[web.1]: [Error] Error: invalid signature: 0x8080014 2017-07-09T20:19:31.408548+00:00 app[web.1]: at /app/node_modules/unzip/lib/parse.js:63:13 2017-07-09T20:19:31.408549+00:00 app[web.1]: at runCallback (timers.js:800:20) 2017-07-09T20:19:31.408550+00:00 app[web.1]: at tryOnImmediate (timers.js:762:5) 2017-07-09T20:19:31.408554+00:00 app[web.1]: at processImmediate [as _immediateCallback] (timers.js:733:5)
Thanks !!! |
I am getting the following error when running node-unzip in combination with a http.get request, then piping it into node-unzip.
The code I use:
tempPath
is defined properly, and the said code works fine on Windows. Now, on my CentOS server, it outputs the error like this:invalid signature: 0x8080014
I'm 100% sure the XML file is valid, the exact file works on Windows.
The text was updated successfully, but these errors were encountered: