microsoft / microsoft/node-request-light
Does this work with `NODE_EXTRA_CA_CERTS`?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 35
- Forks
- 22
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
We have some pretty awesome security software that does this man-in-the-middle-attack TLS interception where it decrypts and re-encrypts all TLS traffic.
For Node apps, I've been able to add the environment variable NODE_EXTRA_CA_CERTS and point it to the security software certificate.
It doesn't seem that this obeys that construct, or perhaps the environment in VS Code extensions isn't seeing that value propagated down? I'm encountering issues while trying to use the Azure Pipelines Language Server that uses this library. It pretty consistently issues a message like: "Error: Unable to get local issuer certificate" and that generally points at this MitM thing.
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 reproducing the certificate error in node-request-light with NODE_EXTRA_CA_CERTS set to the interception certificate, then trace how the library creates HTTPS requests and how the VS Code extension environment reaches it. Compare the behavior with the Azure Pipelines Language Server case; done means the request succeeds with that certificate configured and the relevant behavior is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100