Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow to specify options to the TLS upgrade #195

Closed
wants to merge 1 commit into from
Closed

allow to specify options to the TLS upgrade #195

wants to merge 1 commit into from

Conversation

joerg1985
Copy link

This change relates to the issue #194

@changeset-bot
Copy link

changeset-bot bot commented Jun 1, 2023

⚠️ No Changeset found

Latest commit: 230bf37

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Jun 1, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
proxy-agents ✅ Ready (Inspect) Visit Preview Jun 1, 2023 3:39pm

@joerg1985
Copy link
Author

@TooTallNate could you have a look at this?

@cptRaclette
Copy link

Would be great, if this feature could be added to the package.
Does its job like a charm!

constructor(
proxy: Uri | URL,
opts?: HttpsProxyAgentOptions<Uri>,
upgradeOpts?: tls.ConnectionOptions
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to not introduce a 3rd parameter. This should be a new option on the opts object. Perhaps something like opts.tlsUpgradeOpts.

Additionally, I think this should be an option on the AgentBase class, since http-proxy-agent, https-proxy-agent and socks-proxy-agent all upgrade the socket to TLS using similar logic. We can introduce a helper function (AgentBase#upgradeSocketToTls() or similar) which all of those packages would invoke when appropriate.

Finally, this needs some tests.

@joerg1985
Copy link
Author

I guess this should be done by someone with more experience in typescript.

@joerg1985 joerg1985 closed this Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants