NO_PROXY support

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
nodejs, typescript
Domain
networking

Research direction

Start in src/node/main.ts around lines 268-272, where system proxy settings are read. Trace how the proxy agent is selected for a requested resource, then verify that resources matching NO_PROXY bypass that agent. Done means NO_PROXY is read and matching internal or localhost requests do not use the proxy.

Written by the indexing model from the issue text.

Description

Overview

The library takes provided proxy url or use system configured proxy in environment variable. However, proxies don't work for internal resources and sending request to e.g. localhost or other internal corporate resources fails, depending on proxy configuration.

To do
Dominant language
TypeScript
Stars
35
Forks
22
Avg merge
1d 22h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/node-request-light

All issues in microsoft/node-request-light

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.