On the example below, because of the internal use of new URL to parse the proxy url, the username and password get percent-encoded. This is ideal for URLs, but when we are parsing for username and password for proxy auth, that breaks the strings because the username is converted to username_with_%3D:
new HttpsProxyAgent({
proxy: 'http://username_with_=:password@33.206.125.154:8888',
});```
I have used some proxy providers where there are = chars on the username and for instance on chrome the proxies work fine, but not on hpagent. Should we forcely decoded that on username/password?
On the example below, because of the internal use of
new URL
to parse the proxy url, the username and password get percent-encoded. This is ideal for URLs, but when we are parsing for username and password for proxy auth, that breaks the strings because the username is converted tousername_with_%3D
:I have used some proxy providers where there are
=
chars on the username and for instance on chrome the proxies work fine, but not on hpagent. Should we forcely decoded that on username/password?