Add no_proxy solution
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
It would be nice to exclude certain host names from the proxy. I'm getting the following error which I have no good solution:
```
node-pre-gyp info check checked for "R:\project\node_modules\grpc\src\node\extension_binary\node-v57-win32-x64-unknown\grpc_node.node" (not found)
node-pre-gyp http GET https://storage.googleapis.com/grpc-precompiled-binaries/node/grpc/v1.10.0/node-v57-win32-x64-unknown.tar.gz
node-pre-gyp verb download using proxy url: "http://proxy:8080/"
node-pre-gyp ERR! Tried to download(undefined): https://storage.googleapis.com/grpc-precompiled-binaries/node/grpc/v1.10.0/node-v57-win32-x64-unknown.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for grpc@1.10.0 and node@8.9.4 (node-v57 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp http self signed certificate
```
Note the request is going through a proxy and failing with "self signed certificate", this is understandable, however since there is no option to exclude a host name from the proxy there is no good solution for this issue.
If I could bypass the proxy specifically for a host either through a global config file or an environment variable then it would solve this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the node-pre-gyp HTTP download shown in the report and inspect how the proxy URL is selected. Define the supported configuration or environment-variable behavior for excluding hosts, then verify that requests to the listed storage.googleapis.com URL bypass the proxy while other requests still use it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100