feat(http): enable ssl tunneling through proxy

[Thore1954]

This is similar to #5037 but has a simpler implementation adapted from hpagent and additionally supports HTTPS proxies.

[robertpatrick]

any update on this? I am running into the same issue

[Matthiasvanderhallen]

This looks like a good improvement. I just wanted to remark that it looks like this does not include the fix you provided in PR #5772 which was closed without merging?

[ShemTovYosef]

Hi @Thore1954 don’t you plan to merge it? Any workaround that you can advice ?

[Matthiasvanderhallen]

If it's not against etiquette, I'm willing to make any updates necessary to get this to a point where it can be merged.
Only if @Thore1954 is not planning to champion this further in another branch or something like that, of course...

[Thore1954]

I just wanted to remark that it looks like this does not include the fix you provided in PR #5772 which was closed without merging?

I realized these two PRs would have merge conflicts so I decided to close it and create a new one later. Besides, the issue I pointed out is not only for proxy url auth, but also for target url auth:

axios/lib/adapters/http.js

Lines 357 to 361 in 2701911

	if (!auth && parsed.username) {
	const urlUsername = parsed.username;
	const urlPassword = parsed.password;
	auth = urlUsername + ':' + urlPassword;
	}

Hi @Thore1954 don’t you plan to merge it? Any workaround that you can advice ?

I was indeed expecting a maintainer to merge it at one time. As for the workaround, I am currently using this proxy server which I modified to handle HTTPS requests without tunneling, although it should be used with caution. Alternatively, you could try patching your axios dependency using patch-package.

I'm willing to make any updates necessary to get this to a point where it can be merged. Only if @Thore1954 is not planning to champion this further in another branch

The reason I closed this PR is that it would introduce a breaking change. For the moment, it should be implemented behind a flag, but I would set it as default in the next major release since it aligns with all proxy servers.
I am presently not incentivized to pursue this further since my workaround is working adequately for the time being.

[ShemTovYosef]

Unfortunately we cannot modify the code or use additional server .
As I understood, you don’t have plans to introduce fix in the near future, maybe @Matthiasvanderhallen can continue with it?