You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, first of all thanks for this repo, it's been really useful! I was super happy to see some of the other agents supported username and password auth but haven't been able to get this to work with the pac-proxy-agent.
Simplest pac file I could write for testing:
function FindProxyForURL(url, host) {
return 'PROXY username:password@host:port';
}
Without username:password@ it works like intended.
The text was updated successfully, but these errors were encountered:
I tested this on chrome 114 with the --proxy-pac-url command line flag. Auth seemed to work fine, I'll double check to make sure.
Edit: just read your link, interesting, I suppose chrome is adding some additional logic to make it work, is it worth investigating or should I close this issue in favor of setting up a proxy server in between like suggested in the comments?
Well, one route we could go is to add an option to the PacProxyAgent constructor, where you could specify a pair of hostname:port and the username:password to use when connecting to those proxies. Something like:
Hey, first of all thanks for this repo, it's been really useful! I was super happy to see some of the other agents supported username and password auth but haven't been able to get this to work with the pac-proxy-agent.
Simplest pac file I could write for testing:
Without
username:password@
it works like intended.The text was updated successfully, but these errors were encountered: