create-react-app trying to get compression lib over HTTP instead of HTTPS - failing behind proxy
See original GitHub issueIs this a bug report?
Yes
Did you try recovering your dependencies?
$ npm --version 6.1.0 $ yarn --version 1.7.0
Which terms did you search for in User Guide?
(Write your answer here if relevant.)
Environment
Environment: OS: Windows 7 Node: 10.4.0 Yarn: 1.7.0
Steps to Reproduce
- create-react-app failing behind our corporate proxy. Yarn seems to use HTTP rather than HTTPS to get the ‘compression’ library - my company uses ‘Forcepoint’ and it is blocking HTTP traffic to npmjs. Not sure why this one library is not being fetched via HTTPS.
Note the verbose log output from create-react-app, this happens consistently. Everything up until the compression library works as its getting fetched via HTTPS:
verbose 25.081 Request “https://registry.npmjs.org/object-copy” finished with status code 200. verbose 25.086 Performing “GET” request to “https://registry.npmjs.org/copy-descriptor”. verbose 25.243 Request “https://registry.npmjs.org/copy-descriptor” finished with status code 200. [2/4] Fetching packages… verbose 25.502 Performing “GET” request to “http://registry.npmjs.org/compression/-/compression-1.7.2.tgz”. verbose 25.554 Error: http://registry.npmjs.org/compression/-/compression-1.7.2.tgz: Invalid tar header. Maybe the tar is c orrupted or it needs to be gunzipped? at Object.module.exports.exports.decode (C:\Users\smcgill\AppData\Roaming\npm\node_modules\yarn\lib\cli.js:77578:43) at Extract.onheader (C:\Users\smcgill\AppData\Roaming\npm\node_modules\yarn\lib\cli.js:146111:39)
Expected Behavior
Create a new react app
Actual Behavior
Fails consistently trying to download compression library due to our website filtering infrastructure blocking HTTP traffic to npmjs
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
@rodoabad I was having this issue as well so I looked through the
yarn
issues and found issue #746. Someone had said they disabled their antivirus which solved their problem with socket hang ups. I was running Malwarebytes and upon quitting it, I no longer had this error.I don’t think this is a
create-react-app
issue. More likeyarn
.