Adding an API to configure proxy [$85]

[clowwindy]

In 0.6.3 an API to get proxy for url has been added. Can we have an API to set proxy?

Chrome has a proxy API, which doesn't affect system settings. I'm wondering if nw could have the same feature.

http://developer.chrome.com/extensions/proxy.html

Did you help close this issue? Go claim the $85 bounty on Bountysource.

[xdqi]

Well, I wonder it could develop a method to support PAC file.

wikipedia:http://en.wikipedia.org/wiki/Proxy_auto-config

[wwqgtxx]

like it too......

[erikjjohnson]

Right, can at least nw use the common HTTP_PROXY, http_proxy, HTTPS_PROXY, and https_proxy environment variables when it can't find any system settings?

The PAC and system support in this closed issue is wonderful:

#130

But I've found some linux variants that don't supply the system proxy settings in a way Chrome or nw can understand. In those cases, either using the environment variables or a command line option to set the proxy would be helpful. Of course, the proxy given should be returned by the new API in the above issue

[Pavel-Husakouski]

Actually, it is quite annoying to work behind proxy using NW-application, because users are asked for the credentials twice - first for NW, second for Node

[Pavel-Husakouski]

I think there should be implemented some common way - i.e. environment variable HTTP_PROXY which is accessible from the NW and Node, or, another option, some API

[liclac]

Bump?

The project I'm working on at the moment needs me to find a portable web browser of some sort that runs things through a locally hosted proxy.
node-webkit would be perfect for the task if only I could figure out how to make it use said proxy…

[Pavel-Husakouski]

uppfinnarn: you can't unless the System config is set to your local hosted server. I implemented kind of http client to make nodewebkit working with my own proxy with authentication.

You can use chromium portable if you don't need any node.js modules. It has an extensions that allows you configure the proxy.

[liclac]

Looking at that now, thanks. Not as elegant as I could make my node-webkit solution (where I could run the proxy within the same process), but it works.

[liclac]

Nevermind, Windows only, back to looking for alternatives until (if) this gets addressed...

[felicienfrancois]

Need it too ...

[mkoryak]

+1

[toddhay]

+1 as well

[felicienfrancois]

An API method would be cool but supporting the --proxy-server chromium arg is a first step and is probably easy to implement.

[epodolyak]

+1

[davidrapin]

I support felicienfrancois proposal to support the --proxy-server arg.
For users that cannot edit their system proxy configuration (at work for example), this is really necessary.

[iampuma]

+1 would be very useful

[wells1013]

+1 like it too......

[tholder]

+1

[AlexVBr]

++

[devon]

+1

[devon]

This feature is quite important for Chinese 👍

[cchersin]

+1

[devon]

proxy_service.cc:

#if defined(OS_WIN)
  return new ProxyConfigServiceWin();
#elif defined(OS_IOS)
  return new ProxyConfigServiceIOS();
#elif defined(OS_MACOSX)
  return new ProxyConfigServiceMac(io_thread_task_runner);

I think this is the code to check the system proxy. I will try to 'hard coding' the proxy setting before this issues be fixed.

[Pavel-Husakouski]

Look, there are lots of cases - i.e. when app opens external page that makes ajax requests - credentials are required
When the app uses node http to make some requests. Node http is required to bypass several restrictions of XHR. Credentias are required again

When the password expires or user switches to different network, he must re-enter the credentials . Such cases are impossible to implement

[ayapi]

@rogerwang Thank you for your work!
Any plans to support PAC(Proxy Auto-Config)?
auto_detect and pac_url are in net/proxy/proxy_config.cc
but currently in node-webkit App#setProxyConfig() handles only proxy_rules.
PAC is very useful. Please consider it.

[rogerwang]

@ayapi yeah, would like to support it. Re-open this issue for this.

[alvinteh]

I'd like to add that it seems App.setProxyConfig() does not seem to be working - network requests initiated by Chromium still go use the system proxy settings.

Tested with nw 0.11.2 on CentOS 7 (with GNOME desktop) and Squid proxy.

[brospars]

@tommoor Have you find any solution to autologin in proxy configuration ? My app is meant to run alone without any interaction so I must find a way to do that..

[bestplay]

After gui.App.setProxyConfig Devtools show Empty

With 12.0 & 12.2 for win7 32bit .
And operating system is win7 64bit.

After set proxy by setProxyConfig. and proxy works good.
But Devtools show Empty.

My proxy string pass to setProxyConfig is :
"http=192.168.2.2:8087;https=192.168.2.2:8087;socks=direct://" OR
"http=192.168.2.2:8087;direct://"

Both cause the same result.

Remote debugging via local socket?
And how can I passby the local socket for remote debugging?

[aluxian]

+1 I have the same problem as @bestplay :(

[Zensin]

This can be done by CLI argument in Electron (Previously named Atom Shell) via a commit that was made a while ago right? Should it not now be easy to add to nw.js?

[rogerwang]

@ayapi the support for auto detect proxy and PAC url will be added in the next 0.12.4 release. Thanks for your patience.

[ayapi]

Thank you very much!

[bitnom]

I know a lot of people would love to use nwjs for web automation and so being able to rotate proxies with logins and no user interaction required is essential. There are other use-cases as well.

[jakubnavratil]

Please merge commit by rogerwang c45f686