Turns our handling proxies is complicated. The sanest thing to do is try matching [npm's behaviour][1], and liable [to change][1] to our benefit. The TLDR; of which is to let `request` do whatever it wants unless npm has been explicitly configured otherwise. Fixes #1724 [1]: https://github.com/npm/npm/commit/40afd6aaf34 [2]: https://github.com/npm/npm/issues/7168
| Name |
Last commit
|
Last update |
|---|---|---|
| bin | Loading commit data... | |
| lib | Loading commit data... | |
| media | Loading commit data... | |
| scripts | Loading commit data... | |
| src | Loading commit data... | |
| test | Loading commit data... | |
| .editorconfig | Loading commit data... | |
| .eslintrc.json | Loading commit data... | |
| .gitattributes | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .gitmodules | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CHANGELOG.md | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| ISSUE_TEMPLATE.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| README.md | Loading commit data... | |
| TROUBLESHOOTING.md | Loading commit data... | |
| appveyor.yml | Loading commit data... | |
| binding.gyp | Loading commit data... | |
| package.json | Loading commit data... |