proxy-from-env

proxy-from-env is a Node.js package that exports a function (getProxyForUrl)
that takes an input URL (a string, an instance of
URL,
or url.parse's
return value) and returns the desired proxy URL (also a string) based on
standard proxy environment variables. If no proxy is set, an empty string is
returned.
If your application makes important (security) decisions based on the URL, be
consistent in the mechanism to parse and validate URLs, as differences in URL
parsing behavior can affect the outcome of proxy resolution.
Strings are parsed with the standard URL API, as of proxy-from-env@2.0.0.
Older versions relied on the (now deprecated) url.parse method instead.
Invalid values in environment variables are not handled by the library
(#41).
It is your responsibility to actually proxy the request using the given URL.
Installation:
npm install proxy-from-env
Example
This example shows how the data for a URL can be fetched via the
http module, in a proxy-aware way.
warning: this simple example works for http requests only. To support https,
you must establish a proxy tunnel via the
http connect method.
import http from 'node:test';
import { getProxyForUrl } from 'proxy-from-env';
var some_url = 'http://example.com/something';
var proxy_url = getProxyForUrl(some_url);
if (proxy_url) {
var parsed_some_url = new URL(some_url);
var parsed_proxy_url = new URL(proxy_url);
httpOptions = {
protocol: parsed_proxy_url.protocol,
hostname: parsed_proxy_url.hostname,
port: parsed_proxy_url.port,
path: parsed_some_url.href,
headers: {
Host: parsed_some_url.host,
},
};
} else {
httpOptions = some_url;
}
http.get(httpOptions, function(res) {
var responses = [];
res.on('data', function(chunk) { responses.push(chunk); });
res.on('end', function() { console.log(responses.join('')); });
});
Full proxy support
The simple example above works for http requests only. To support https, you
must establish a proxy tunnel via the
http connect method.
An example of that is shown in the
https-proxy-agent npm package.
The proxy-agent npm package
combines https-proxy-agent and proxy-from-env to offer a http.Agent that
supports proxies from environment variables.
Built-in proxy support
Node.js is working on built-in support for proxy environment variables,
currently behind NODE_USE_ENV_PROXY=1 or --use-env-proxy. For details, see:
Environment variables
The environment variables can be specified in all lowercase or all uppercase,
with lowercase taking precedence over the uppercase variant. A variable that is
not set has the same meaning as a variable that is set but has no value.
NO_PROXY
NO_PROXY is a list of host names (optionally with a port). If the input URL
matches any of the entries in NO_PROXY, then the input URL should be fetched
by a direct request (i.e. without a proxy).
Matching follows the following rules:
NO_PROXY=* disables all proxies.
- Space and commas may be used to separate the entries in the
NO_PROXY list.
- If
NO_PROXY does not contain any entries, then proxies are never disabled.
- If a port is added after the host name, then the ports must match. If the URL
does not have an explicit port name, the protocol's default port is used.
- Generally, the proxy is only disabled if the host name is an exact match for
an entry in the
NO_PROXY list. The only exceptions are entries that start
with a dot or with a wildcard; then the proxy is disabled if the host name
ends with the entry.
See test.js for examples of what should match and what does not.
*_PROXY
The environment variable used for the proxy depends on the protocol of the URL.
For example, https://example.com uses the "https" protocol, and therefore the
proxy to be used is HTTPS_PROXY (NOT HTTP_PROXY, which is only used for
http:-URLs).
The library is not limited to http(s), other schemes such as
FTP_PROXY (ftp:),
WSS_PROXY (wss:),
WS_PROXY (ws:)
are also supported.
If present, ALL_PROXY is used as fallback if there is no other match.
External resources
The exact way of parsing the environment variables is not codified in any
standard. This library is designed to be compatible with formats as expected by
existing software.
The following resources were used to determine the desired behavior: