-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
TypeError: Request path contains unescaped characters #1021
Comments
You can sort of figure most of it out from the error message above, but just to be clear: This is on Windows 7 with node v5.9. I've also tried 5.12, 6.4 and 6.5 |
I can manually download the header files and specify the path to them with --tarball, but then I get stuck on issue #1002 And even if that would have worked it wouldn't have been a good solution in the long run :) |
That 'Request path contains unescaped characters' means there is a space in the request path (because that's all node.js core checks for.) I don't know exactly what goes wrong but apparently something somewhere is letting a blank slip through. |
Any idea how to debug this further? |
Not really. Maybe add a few console.log statements to tunnel-agent/index.js? |
If I manually run |
This is the output I get when I try to install a package that needs node-gyp (node-sass in this case):
The error message at the core of it all seems to be "TypeError: Request path contains unescaped characters". Which is very confusing, because google seems to suggest it's something wrong with my proxy settings. But I don't know what it could be.
Some relevant information about my system setup:
What is wrong/missing in my setup?
The text was updated successfully, but these errors were encountered: