Expand interface to support url/protocol specific results.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I was just checking before I create a new npm module, I wanted to do something similar, but have a URL passed in, then check against the NO_PROXY list, and from there check for a protocol specific proxy, and fallback to ALL_PROXY and from there returning null if no match.
I already created the no-proxy module to check the first part, and was about to create a new module for the get-proxy. Would you be open to a PR?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing get-proxy interface and the linked no-proxy module to understand how proxy configuration is currently exposed. The work is done when a URL is checked against NO_PROXY, protocol-specific proxies are selected, ALL_PROXY is used as fallback, and null is returned when nothing matches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100