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

Properly differintiate http and https proxies #7187

Conversation

Torbjorn-Svensson
Copy link

options.secureEndpoint is not always defined. There is however, a function to properly identify the type of connection in the base class, so intead of rolling the own check, relly on the base class implementation.

Fixes #7024

Contributed by STMicroelectronics

References

options.secureEndpoint is not always defined. There is however, a
function to properly identify the type of connection in the base
class, so intead of rolling the own check, relly on the base class
implementation.

Fixes npm#7024

Contributed by STMicroelectronics

Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
@Torbjorn-Svensson Torbjorn-Svensson requested a review from a team as a code owner January 31, 2024 09:19
@Torbjorn-Svensson
Copy link
Author

I also did the same thing here: npm/agent#92

@wraithgar
Copy link
Member

npm/agent#92

@wraithgar wraithgar closed this Jan 31, 2024
@Torbjorn-Svensson Torbjorn-Svensson deleted the pr/fix-http-https-proxy-selection branch January 31, 2024 15:45
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.

[BUG] npm@10 refuses to install packages from GitHub package registry
2 participants