Filter tls options
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 880
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
Determine which tls options actually make sense to forward to tls.connect and throw if any other is provided (e.g. allowHalfOpen).
Contributor guide
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 tracing the code path that forwards options to Node.js tls.connect. Compare the forwarded options with tls.connect's supported options and inspect any existing TLS option tests. Done means unsupported options such as allowHalfOpen are rejected while valid TLS options continue to be forwarded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100