diff --git a/CHANGELOG.md b/CHANGELOG.md index f4e3f85..9154a76 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -17,7 +17,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0. - `n run` with legacy aliases of `as` and `use` - `n lsr` for listing matching remote versions, limited to 20 by default ([#383]) - `n doctor` for displaying diagnostic information -- `n install` for people used to other products with this command +- `n install` for people used to other products with this command ([#524]) - `--insecure` to disable curl/wget certificate checks - added npm version to installed message ([#210] [#484] [#574]) @@ -181,6 +181,7 @@ Only minor functional changes, but technically could break scripts relying on sp [#518]: https://github.com/tj/n/issues/518 [#521]: https://github.com/tj/n/issues/521 [#522]: https://github.com/tj/n/issues/522 +[#524]: https://github.com/tj/n/issues/524 [#528]: https://github.com/tj/n/issues/528 [#529]: https://github.com/tj/n/issues/529 [#531]: https://github.com/tj/n/issues/531 diff --git a/docs/proxy-server.md b/docs/proxy-server.md new file mode 100644 index 0000000..394035e --- /dev/null +++ b/docs/proxy-server.md @@ -0,0 +1,94 @@ +# Proxy Server + +Under the hood, `n` uses `curl` or `wget` for the downloads. `curl` is used if available, and `wget` otherwise. Both `curl` and `wget` support using environment variables or startup files to set up the proxy. + +## Using Environment Variable + +You can define the proxy server using an environment variable, which is read by multiple commands including `curl` and `wget`: + + export https_proxy='http://host:port/path' + +If your proxy requires authentication you can [url-encode](https://urlencode.org) the username and password in the URL. e.g. + + export https_proxy='http://user:password@host:port/path' + +If you have defined a custom node mirror which uses http, then you would define `http_proxy` rather than `https_proxy`. + +## Certificate Checks + +Your proxy server may supply its own ssl certificates for remote sites (as a man-in-the-middle). If you can not arrange to trust the proxy in this role, you can turn off (all) certificate checking with `--insecure`. e.g. + + n --insecure --lts + +Another possible work-around for certificate problems is to use plain http by specifying a custom node mirror: + + export NODE_MIRROR='http://nodejs.org/dist' + export http_proxy='http://host:port/path' + n --lts + +## Startup Files + +An alternative to using an environment variable for the proxy settings is to configure a startup file for the command. + +Example `~/.curlrc` ([documentation](https://ec.haxx.se/cmdline-configfile.html)) + + proxy = http://host:port/path + proxy-user = user:password + # If need to disable certificate checks + --insecure + +Example `~/.wgetrc` ([documentation](https://www.gnu.org/software/wget/manual/html_node/Wgetrc-Commands.html#Wgetrc-Commands)) + + https_proxy = http://host:port/path + proxy_user = user + proxy_password = password + # If need to disable certificate checks + check_certificate = off + +## Troubleshooting + +To experiment and find what settings you need, use `curl` (or `wget`) directly with the node mirror and check the error messages. + +For these examples there is a proxy running on localhost:8080 which does not require authentication, but the certificates it offers +are not trusted. + +First try fails because of the certificates and `curl` helpfully explains: + + $ curl --proxy localhost:8080 https://nodejs.org/dist/ + curl: (60) SSL certificate problem: self signed certificate in certificate chain + ... + If you'd like to turn off curl's verification of the certificate, use + the -k (or --insecure) option. + HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure. + +Once you get the command to work with settings appropriate for your setup, like: + + $ curl --insecure --proxy localhost:8080 https://nodejs.org/dist/ + +