Invalid proxy settings #41
Comments
|
Thanks for reporting! I'll try to take a look soon-ish. |
|
I'm looking into this. I created a test case in this branch: https://github.com/tebeka/selenium/blob/topic/add-proxy-test/remote_test.go#L1190 Setting the proxy in the expected way works for Chrome and ChromeDriver. It does not work for Firefox 47 in Selenium2, the latest Firefox Nightly in Selenium3, or the latest Firefox Nightly directly through Geckodriver. I posted these details on this Geckodriver issue: mozilla/geckodriver#470 It has been suggested to not use the Proxy settings for Selenium2, but use the Preferences settings. I can't seem to get that to work either |
|
I have successfully used an HTTP proxy via both Firefox 47 and Selenium 2.x and Firefox Nightly through Geckodriver (in addition to Chrome and Chromedriver). Using Selenium 3 doesn't work, due to an error from Selenium 3: For recent versions of Firefox (48+), both Proxy.HTTP and Proxy.HTTPPort (or SSLPort or SocksPort) need to be set, the former with just the host name and the latter with just the port number. See https://github.com/tebeka/selenium/blob/topic/add-proxy-test/remote_test.go#L1385 as an example. I'll commit that soon once I debug the Selenium 3 bug more. |
The current state of using a Proxy is both well-defined and variously implemented. * Chrome and ChromeDriver uses just the HTTP field with a host:port. * Firefox via GeckoDriver directly requires that the host be provided in the HTTP field and the port be provided in the HTTPPort field. * Firefox via Selenium 2 uses just the HTTP field, with the caveat that connections to localhost are not proxied, by default. An additional preference is needed to unset this. * Firefox via Selenium 3 and GeckoDriver fails because Selenium adds a whole bunch of "nulls" for unset values in the Proxy object, which Marionette does not like. mozilla/geckodriver#490 Fixes #41.
The current state of using a Proxy is both well-defined and variously implemented. * Chrome and ChromeDriver uses just the HTTP field with a host:port. * Firefox via GeckoDriver directly requires that the host be provided in the HTTP field and the port be provided in the HTTPPort field. * Firefox via Selenium 2 uses just the HTTP field, with the caveat that connections to localhost are not proxied, by default. An additional preference is needed to unset this. * Firefox via Selenium 3 and GeckoDriver fails because Selenium adds a whole bunch of "nulls" for unset values in the Proxy object, which Marionette does not like. mozilla/geckodriver#490 Fixes #41.
The current state of using a Proxy is both well-defined and variously implemented. * Chrome and ChromeDriver uses just the HTTP field with a host:port. * Firefox via GeckoDriver directly requires that the host be provided in the HTTP field and the port be provided in the HTTPPort field. * Firefox via Selenium 2 uses just the HTTP field, with the caveat that connections to localhost are not proxied, by default. An additional preference is needed to unset this. * Firefox via Selenium 3 and GeckoDriver fails because Selenium adds a whole bunch of "nulls" for unset values in the Proxy object, which Marionette does not like. mozilla/geckodriver#490 Fixes #41.
tebeka/selenium version 0.9.2
selenium-server version 3.0.1 and 2.53.1
firefox version 49.0.1
Code specified inside the proxy is invalid, firefox network options display "system settings.".
Tested python version, the agent can work properly.
I checked the information in the afternoon did not determine what the problem is, how should the agent should be installed?
selenium-server log
Also tested 3.0.1, the same can not set the agent
The text was updated successfully, but these errors were encountered: