emarock / proxy-pac-proxy Goto Github PK

Hi, I was wondering if proxy-pac-proxy supports changing environments.

For example, I will start proxy-pac-proxy with a PAC url, which will work while I'm at work.
But when I go home, how will it behave? In such case, does proxy-pac-proxy simply act as a forwarding proxy directly to the destination host without forwarding any traffic to an upstream proxy? (as none would be defined, since no PAC would be reachable when I'm at home).

After macOS upgrade to Mojave node begins surfacing client connection resets as ECONNRESET errors. Need to catch and handle, as otherwise the daemon crashes badly.

cool stuff, maybe update the deps though?

❯ npm install -g proxy-pac-proxy

changed 168 packages, and audited 169 packages in 3s

15 vulnerabilities (7 moderate, 3 high, 5 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

also bluebird is "dead" (native promises), not sure if async is needed anymore either...

Is proxy-pac-proxy supporting multiple proxies failover?
like this: https://en.wikipedia.org/wiki/Proxy_auto-config#Advanced_functionality
Or example code(from McAfee):

function FindProxyForURL(url, host) {
    if (dnsDomainIs(host, ".company.com")\ | \ | isInNet(host, "10.1.1.0", "255.255.255.0")\ | \ | isInNet(host, "192.168.1.0", "255.255.255.0"))
        return "DIRECT";
    else if (isInNet(myIPAddress(), "10.1.1.0", "255.255.255.0"))
        return "PROXY proxy01.company.com:9090; proxy02.company.com:9090";
    else
        return "PROXY proxy03.company.com:9090; proxy02.company.com:9090";
}

And thanks for your work. Saving my day!

After macOS upgrade to Mojave, node begins surfacing connection resets on client side as ECONNRESET errors. This crashes the daemon pretty badly.