Retrieve proxy settings specified by the system
Перейти к файлу
dependabot[bot] 1002fe0d9b
Build(deps): Bump ini from 1.3.5 to 1.3.8 (#28)
Bumps [ini](https://github.com/isaacs/ini) from 1.3.5 to 1.3.8.
- [Release notes](https://github.com/isaacs/ini/releases)
- [Commits](https://github.com/isaacs/ini/compare/v1.3.5...v1.3.8)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2021-02-23 12:20:50 -05:00
.vscode Feature: Proxy validation and authentication (#6) 2018-02-06 14:32:06 -08:00
src Fix command injection vulnerability when running registry executable. (#29) 2021-02-23 12:19:59 -05:00
.editorconfig Retrieve proxy settings for windows and initial code (#1) 2018-02-05 14:17:09 -08:00
.gitignore Retrieve proxy settings for windows and initial code (#1) 2018-02-05 14:17:09 -08:00
.mocharc.json Update mocha version & Fix typing for getWindowsProxy (#26) 2020-08-17 07:41:35 -07:00
.npmignore Fix: ProxyEnable being ignored (#16) 2018-05-29 10:01:46 -07:00
.travis.yml Update mocha version & Fix typing for getWindowsProxy (#26) 2020-08-17 07:41:35 -07:00
CHANGELOG.md Update mocha version & Fix typing for getWindowsProxy (#26) 2020-08-17 07:41:35 -07:00
LICENSE Initial commit 2018-02-05 11:26:16 -08:00
Readme.md Fix command injection vulnerability when running registry executable. (#29) 2021-02-23 12:19:59 -05:00
package-lock.json Build(deps): Bump ini from 1.3.5 to 1.3.8 (#28) 2021-02-23 12:20:50 -05:00
package.json Fix command injection vulnerability when running registry executable. (#29) 2021-02-23 12:19:59 -05:00
tsconfig.json Build (#7) 2018-02-06 14:49:58 -08:00
tslint.json Fix: ProxyEnable being ignored (#16) 2018-05-29 10:01:46 -07:00

Readme.md

Note: This project is not actively maintained. If some issues come up we'll look into fixing them but new features will most likely not make it.

System Proxy

Build Status npm version

This library support

  • Reading proxy settings from the HTTP_PROXY or HTTPS_PROXY environment variables
  • Reading proxy settings from the HTTP_PROXY or HTTPS_PROXY node configuration
  • Retrieving the settings from the internet settings on Windows in the registry
  • Validating the connection and asking for credentials if needed
  • Note that it doesn't support every proxy system. If you are using electron it is recommended to use electron/chromium built in proxy support which is much more advanced.

Install

npm install --save get-proxy-settings

Usage

Import

// With named import
import { getProxySettings, getAndTestProxySettings } from "get-proxy-settings";

// Or with commonjs
const { getProxySettings, getAndTestProxySettings } = require("get-proxy-settings");

Use


async function basic() {
    const proxy = await getProxySettings();
    console.log("proxy", proxy.http, proxy.https);
}

// Get and validate the proxy settings
async function withValidation() {
    async function login() {
        // Do any async operation to retrieve the username and password of the user(prompt?)
        return {username: "abc", password: "123"}
    }

    const proxy = await getAndTestProxySettings(login);
    console.log("proxy", proxy.http, proxy.https);
}

Config

Update the test url (Which url is used to validate the proxy)

import { defaults } from "get-proxy-settings";

defaults.testUrl = "https://example.com";

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Credits

  • Timothee Guerin
  • Adar Zandberg from the CxSCA AppSec team at Checkmarx. (Finding Command injection vulnerability)