@@ -37,11 +37,13 @@ The company running npm has a list of common troubleshooting situations [here](h
38### Firewalls
38### Firewalls
40−Some companies have a firewall and want to route traffic through a proxy server.
40+Some companies have a firewall.
42−Usually that means you have a `HTTPS_PROXY` environment variable set on your computer.
42+These companies usually have set the `HTTP_PROXY` or `HTTPS_PROXY` environment variable on your computer. This is more common with Windows computers.
44−If you want to try to set it temporarily to see what happens, you can try something like this:
44+The result is that the request for `https://github.com/elm/compiler/releases/download/0.19.1/binary-for-windows-64-bit.gz` is being sent to a "proxy server" where they monitor traffic. Maybe they rule out certain domains, maybe they check data when it comes back from the actual URL, etc.
46+It is probably best to ask someone about the situation on this, but you can test things out by temporarily using an alternate `HTTPS_PROXY` value with something like this:
47# Mac and Linux
49# Mac and Linux
@@ -52,6 +54,8 @@ set HTTPS_PROXY=http://proxy.example.com
52npm install -g elm
54npm install -g elm
57+Check out [this document](https://www.npmjs.com/package/request#controlling-proxy-behaviour-using-environment-variables) for more information on how environment variables like `NO_PROXY`, `HTTP_PROXY`, and `HTTPS_PROXY` are handled by the npm.