Proxy Auto-Authentication?

1,535 views
Skip to first unread message

Trevor Haba

unread,
Apr 3, 2015, 5:58:46 PM4/3/15
to chromi...@chromium.org
I am attempting to run google chrome on a headless server, controlled by selenium. I need to use a forward proxy (squid in this case) for my tests. Is there a way to include the authenticating username and password to the proxy so that I don't need to authenticate myself? I am using the command line flag --proxy-server="host:port" to specify the proxy. The convention --proxy-server="username:password@host:port" results in an error "no supported proxies" in the dev tools console. Is there a command line argument I can use or a setting somewhere that I can set to auto authenticate? Keep in mind that the server is headless, I can't navigate to chrome://flags or something within the chrome window to set the password.

Ryan Sleevi

unread,
Apr 3, 2015, 6:13:28 PM4/3/15
to trevo...@paperg.com, net-dev
-chromium-dev
+net-dev

On Fri, Apr 3, 2015 at 2:58 PM, Trevor Haba <trevo...@paperg.com> wrote:
I am attempting to run google chrome on a headless server, controlled by selenium. I need to use a forward proxy (squid in this case) for my tests. Is there a way to include the authenticating username and password to the proxy so that I don't need to authenticate myself? I am using the command line flag --proxy-server="host:port" to specify the proxy. The convention --proxy-server="username:password@host:port" results in an error "no supported proxies" in the dev tools console. Is there a command line argument I can use or a setting somewhere that I can set to auto authenticate? Keep in mind that the server is headless, I can't navigate to chrome://flags or something within the chrome window to set the password.

Command-line flag? No. 

An extension with webRequest permissions can use https://developer.chrome.com/extensions/webRequest#event-onAuthRequired

Trevor Haba

unread,
Apr 6, 2015, 2:44:55 PM4/6/15
to chromi...@chromium.org, trevo...@paperg.com, net...@chromium.org, rsl...@chromium.org
I see. That is disappointing, but thanks for the update
Reply all
Reply to author
Forward
0 new messages