Supporting proxies?

[brad...@roboticprofit.com]

Hi,

Thanks for working on this. It rules.

Is there any way I can get HTTP Basic Auth proxies to work with headless mode? Right now, I have a little extension that handles configuring chrome.proxy.settings. But since headless mode doesn't support extensions, this won't work. You can't access a proxy with username/password by env vars or on the CLI. 

I'm using one proxy per process/window, so setting it at the system level doesn't make sense. 

Thanks!

Cheers,

B

[burtona...@gmail.com]

I haven't tried this but you MIGHT try http://user:pa...@example.com/ as a proxy... 

It's a pseudo standard and not always supported but it has a good chance of working.

--proxy is supported on teh command line.

[Bradford Stephens]

I've already tried that -- sadly, it does not work :(

--

----

Bradford Stephens

CEO, RoboticProfit

[burtona...@gmail.com]

Can you use a PAC script for this?  

I always find PAC scrips a bit of a hack but this could work.

[Bradford Stephens]

PAC scripts don't support hardcoded user/password -- but good thinking :)

[Eric Seckler]

Hmm, the command line option would be --proxy-server. But I'm not sure if ProxyConfig even supports configuring passwords statically - it seems to use hostname/port pairs only. What does your extension do to configure the password?

Maybe it would help to understand why you'd like to (authenticate to and) use different proxies from headless instances. Could you alternatively run a local proxy that does the authentication to the actual proxy for you?

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.
To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/CAAeOc3NX2RJ_i%3D49%2Bk-X8FCAuEjsAW2MUK8-C8-k-xYbNgCM3Q%40mail.gmail.com.

[Bradford Stephens]

I appreciate the help. I just use chrome.proxy.settings.set in my extension. 

And you're right. I could just run a local proxy. I think I'll do that instead -- I was just hoping to have one less moving component ;)

To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev+unsubscribe@chromium.org.

To post to this group, send email to headle...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/CAAeOc3NX2RJ_i%3D49%2Bk-X8FCAuEjsAW2MUK8-C8-k-xYbNgCM3Q%40mail.gmail.com.

[Georgios Diamantopoulos]

Hi Eric,

Running a local proxy could quickly get problematic if different tabs need to use a different proxy.

Wait, first of all, is that even possible? To set the proxy per tab instead of per browser? 

Then, how is it not possible to authenticate against the proxy? I mean is it just that's not coded in headless yet or?

Could you give some pointers to its implementation?

Thank you

[Sami Kyostila]

We don't support proxy authentication right now because the shell only understands a basic host:port proxy setting: crbug.com/681521. If anyone would like to contribute patches to do this we'll gladly help land them.

- Sami

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/790d389d-24f9-4326-8a73-6ae198271a36%40chromium.org.

[Georgios Diamantopoulos]

I need that functionality so I'm definitely willing to give it a shot. Some bullet-point pointers please?

[Sami Kyostila]

I'm not an expert on proxies, but based on a quick code search I think we'd need to implement a net::URLRequest::Delegate and implement the OnAuthRequired method. In normal Chrome that method pops up a dialog:

https://cs.chromium.org/chromium/src/content/browser/loader/resource_loader.cc?rcl=8401d78afcd1cf80cbe547f597b3bad9edf83694&l=369

In headless mode we'd probably need to read the proxy settings from the command line.

- Sami

[Georgios Diamantopoulos]

Sounds easy enough. I'll dig up the contributing guide and get started.

[bas...@b26.co]

has there been any progress on this?

[Alex Clarke]

If you mean protocol support for responding to HTTP 407 auth challenges then yes support for that has landed.  If a Network.requestIntercepted event contains an authChallenge property then you can call continueInterceptedRequest with an authChallengeResponse to provide the user name and password.

--

You received this message because you are subscribed to the Google Groups "headless-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev+unsubscribe@chromium.org.

To post to this group, send email to headle...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/f2bf8ff8-4023-4d67-b0ab-155a4193ce47%40chromium.org.

[Bashir Osman]

Hi Alex, 

From my understand, this will only work if you use Chrome DevTools Protocol? Is there anyway I can pass the username and password as a command line? I'm running Chrome using Selenium. 

Cheers

On Friday, July 7, 2017 at 1:21:37 AM UTC-6, Alex Clarke wrote:

If you mean protocol support for responding to HTTP 407 auth challenges then yes support for that has landed.  If a Network.requestIntercepted event contains an authChallenge property then you can call continueInterceptedRequest with an authChallengeResponse to provide the user name and password.

On 6 July 2017 at 18:18, <bas...@b26.co> wrote:

has there been any progress on this?

On Wednesday, January 4, 2017 at 2:48:49 PM UTC-7, brad...@roboticprofit.com wrote:

Hi,

Thanks for working on this. It rules.

Is there any way I can get HTTP Basic Auth proxies to work with headless mode? Right now, I have a little extension that handles configuring chrome.proxy.settings. But since headless mode doesn't support extensions, this won't work. You can't access a proxy with username/password by env vars or on the CLI. 

I'm using one proxy per process/window, so setting it at the system level doesn't make sense. 

Thanks!

Cheers,

B

--
You received this message because you are subscribed to the Google Groups "headless-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev...@chromium.org.

To post to this group, send email to headle...@chromium.org.

[cheera...@gmail.com]

 I also need this feature, looking forward to any solution for it.

[mik...@gmail.com]

I'd like to see this feature too, subscribing.

[s...@mck-enzies.com]

Any updates?

[Alex Clarke]

Is there some reason why you can't use DevTools protocol to provide the credentials?

--

You received this message because you are subscribed to the Google Groups "headless-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev+unsubscribe@chromium.org.

To post to this group, send email to headle...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/66245e3d-f59b-47b0-8279-531941846001%40chromium.org.

[Aiden]

Also hoping to see this feature added. 

[Alex Clarke]

On 24 January 2018 at 15:31, 'Aiden' via headless-dev <headle...@chromium.org> wrote:

Also hoping to see this feature added. 

I doubt that will happen.  Is there some reason why you can't use DevTools protocol?

 

On Sunday, October 22, 2017 at 12:10:44 PM UTC-5, mik...@gmail.com wrote:

I'd like to see this feature too, subscribing.

--

You received this message because you are subscribed to the Google Groups "headless-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to headless-dev+unsubscribe@chromium.org.
To post to this group, send email to headle...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/7c3b71a7-fbca-4a7f-98f8-e1d462a4bc94%40chromium.org.

[Joel Griffith]

You should be able to do this already, as Chrome has support for proxies when you launch with the appropriate CLI switch. After that, the library has to support it via dev-tools (as mentioned above). Puppeteer can do this here: https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#pageauthenticatecredentials

The service I run (browserless) supports this out-of-the-box: https://docs.browserless.io/configuration/parameters/

On Wednesday, January 4, 2017 at 1:48:49 PM UTC-8, brad...@roboticprofit.com wrote:

[Aiden Yang]

Thanks! I wasn't aware that puppeteer supported proxy auth. I'll check it out  

--
You received this message because you are subscribed to a topic in the Google Groups "headless-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/headless-dev/KOR84u-FNU0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to headless-dev...@chromium.org.

To post to this group, send email to headle...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/headless-dev/5465551f-edef-49b9-ac34-1d6eb18b7e45%40chromium.org.

[mich...@gmail.com]

Hello, 

after few days of digging I found some solution, or more of a workaround. you still cant access proxy directly, but you can create new local transparent proxy, on which you can then connect. it is not very elegant solution, as you have to have another process running, but on the other hand it's quite clean

code here: https://github.com/sjitech/proxy-login-automator 

On Wednesday, 4 January 2017 22:48:49 UTC+1, brad...@roboticprofit.com wrote: