Add Proxy Exceptions to Phantom

[h4wlt]

Hi,

I have set a system proxy on my machine and when running my tests (in Protractor) all of the requests go via the proxy. This is good, however I want to add some proxy exceptions to allow me to navigate to our qa environment but still be able to download the external analytics objects etc.

Is there a way to issue proxy exceptions to Phantom?

Thanks,
Craig.

[h4wlt]

Ok, so I added the following to the webdriver capabilities section:

  'proxy': {
      'proxyType': 'manual',
      'httpProxy': 'http://proxy.blah.co.uk:8080'
      'httpsProxy': 'http://proxy.blah.co.uk:8080'
      'noProxy': 'blah.blah.co.uk,*blah.blah.co.uk,.blah.blah.co.uk'
  }

},

The proxy setting is being picked up but the noProxy isn't kicking in (the tests are still resolving the address via the proxy and hitting the live site).

I have also tried adding the following as environment variables but still the tests are resolving via the proxy -

export no_proxy=127.0.0.1,localhost,.something.something.co.uk
export no_proxy=127.0.0.1,localhost,*something.something.co.uk
export no_proxy=127.0.0.1,localhost,something.something.co.uk
export no_proxy="127.0.0.1,localhost,.something.something.co.uk"
and the same with caps for the NO_PROXY part

Does Phantom support proxy exclusions and if so what format are they required to be in?

I found the ProxyJsonObject here:
https://code.google.com/p/selenium/wiki/DesiredCapabilities#Proxy_JSON_Object

Thanks,
Craig

[h4wlt]

I have just run Phantom as a standalone instance and set the no_proxy environment variable and I can confirm it doesn't honour it. I am not aware of any other way of adding proxy exceptions to this browser so will start looking at building a new internal proxy server to get around the issue.

[jefleponot]

#12131
the feature has been developped but never add to the main project. :-(

[abnun]

We would also need this feature ... is there any timeline when it will be available?

[stale]

Due to our very limited maintenance capacity (see #14541 for more details), we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed. In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution!