Firefox ignores desiredCapabilities proxy settings

[tnguyen14]

Meta -

Image(s):
standalone-firefox, standalone-firefox-debug
Docker-Selenium Image Version(s):
3.1.0
OS:
RHEL 7.3

With the following proxy settings:

desiredCapabilities: {
  proxy: {
    proxyType: 'manual',
    httpProxy: 'proxy.corp.com:8080',
    sslProxy: 'proxy.corp.com:8080',
    noProxy: 'localhost'
  } 
}

Expected Behavior -

The browser session will use the proxy settings

Actual Behavior -

Proxy is not observed in Firefox. It works when using the chrome versions however (standalone-chrome and standalone-chrome-debug).

[diemol]

@tnguyen14
Googling for a while, I realised that the proxy attributes are not the same for Chrome and Firefox (at least now). Check https://github.com/mozilla/geckodriver#proxy-object for the correct ones.

For example, in Chrome you pass httpProxy: 'proxy.corp.com:8080', but it seems that in Firefox you need to pass: {httpProxy: "proxy.corp.com", httpProxyPort: 8080}.

[tnguyen14]

@diemol I just tried your suggestion, but that doesn't seem to make a difference.

[diemol]

@tnguyen14 my suggestion was more to check how Geckodriver expects the proxy info in the capabilities, did yo check that?

[tnguyen14]

@diemol From searching around, I found the same results that you mentioned, i.e. httpProxy and httpProxyPort as separate properties.

[diemol]

@tnguyen14 exactly, so I think you need to reflect that in your code. Basically Firefox profiles have different properties. It is not an issue of docker-selenium I think.

[tnguyen14]

Right. And when I updated the properties to use those specific to firefox, it still did not work.

[diemol]

Perhaps you can post that problem here and reference this issue? https://github.com/mozilla/geckodriver
Since it seems clearly related to the Firefox options.

[tnguyen14]

I just looked at the options again, and it seems like they don't support the noProxy option anymore? Do you know if there's a different way to set that?

[diemol]

Not really, I have never used Firefox profiles in that way. I just noticed that the settings are different from Chrome profiles.
Maybe it is better to ask them directly❓

[tnguyen14]

I asked the question in mozilla/geckodriver#725

[tnguyen14]

I was told that webdriver does not support noProxy, so I raised it in w3c/webdriver#913

[tnguyen14]

One thing I've noticed is that the node-firefox version will respect environment variables set for http_proxy and no_proxy, but the node-firefox-debug version will not. What do you think might cause this difference?

[diemol]

@tnguyen14 that should get fixed when #477 gets solved.

Aside from that, it seems that the noProxy thing is being handled in the issue you raised at the w3c project.

Since this is not a docker-selenium issue, could you please close this issue?

Thanks!

[tnguyen14]

Thanks @diemol. Any estimate on when you think #477 will land?