-
Notifications
You must be signed in to change notification settings - Fork 133
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
Upgrade https-proxy-agent ^5.0.1 to ^7.0.2 #679
Conversation
bfd9430
to
f3a54cd
Compare
I'm following up on your comment on my other PR: #496 (comment) I submitted this PR to upgrade the See the description:
|
Hi @jportner |
Thank you! Let me know if I can help at all. |
Hello @jportner, @sfc-gh-pmotacki , Thank you for the great work. Any update on this PR? Let me know if I can help you on this PR. |
This is still on my side. I am trying to arrange time to complete the planned work and confirm that the changes are ready for merging. |
@jportner One more time thank you for you contribution. After tests I added some small fixes and finally I merged your change in pr 689. |
Changes was merged in PR #689 |
Description
Resolves #491.
This is a follow-on to #641. That PR fixed socket keepAlive for direct connections. However, keepAlive currently does not work on proxied connections, because https-proxy-agent 5.x closes connections prematurely. (The maintainer of that package added support for keepAlive in version 6.0.0).
This PR upgrades https-proxy-agent to ^7.0.2, so keepAlive will work for proxied connections.
Checklist
npm run lint:check -- CHANGED_FILES
and fix problems in changed code)npm run test:unit
andnpm run test:integration
)Testing
I tested that the upgraded package still works by running a local proxy and using these environment variables to run the "testProxy" system test:
Output: