Proxy configuration capability for Microsoft WebDriver

External Issue #5468949

Details

Created
Nov 18, 2015
Privacy
This issue is public.
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

For example:
$ curl -sd “{’desiredCapabilities’: {’browserName’: 'MicrosoftEdge’, 'proxy’: { 'httpProxy’: '127.0.0.1:9999’, 'ftpProxy’: '127.0.0.1:9999’, 'sslProxy’: '127.0.0.1:9999’, 'noProxy’: None, 'proxyType’: 'MANUAL’, 'class’: 'org.openqa.selenium.Proxy’, 'autodetect’: False }}}” “http://127.0.0.1:26665/wd/hub/session

The actual capabilities sent back by the Microsoft WebDriver server do not include the ‘proxy’ capability, indicating that the proxy was not configured.

Expected Results:

Microsoft WebDriver should respect the ‘proxy’ desired capability.

Actual Results:

Dev Channel specific:

No

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Mara P.”

      Changed Assigned To from “Mara P.” to “Clay M.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Clay M.” to “IE S.”

      Changed Status from “Confirmed” to “External”

    • I see the same issue when try to configure Edge Driver to use proxy.
      I use Java Webdriver. The code example is below:

      BrowserMobProxy proxy = new BrowserMobProxyServer();
      proxy.start(0);

      Proxy seleniumProxy = ClientUtil.createSeleniumProxy(proxy);
      DesiredCapabilities capabilities = DesiredCapabilities.edge();
      capabilities.setCapability(CapabilityType.PROXY, seleniumProxy);
      capabilities.setCapability(CapabilityType.ACCEPT_SSL_CERTS, true);

      System.setProperty("webdriver.edge.driver", “path_to_Edge_driver”);
      WebDriver driver = new EdgeDriver(capabilities);
      System.out.println(((EdgeDriver)driver).getCapabilities().toString());

      The latest instruction does output for used Capabilities and it doesn’t contain information for proxy:
      Capabilities [{applicationCacheEnabled=true, acceptSslCerts=true, browserVersion=38.14393.1066.0, platformVersion=10, locationContextEnabled=true, webStorageEnabled=true, browserName=MicrosoftEdge, takesScreenshot=true, pageLoadStrategy=normal, takesElementScreenshot=true, platformName=windows, platform=ANY}]

      In the case I use similar code for IE I see output below which contains information for proxy:
      Capabilities [{browserAttachTimeout=0, ie.enableFullPageScreenshot=true, enablePersistentHover=true, ie.forceCreateProcessApi=false, ie.forceShellWindowsApi=false, pageLoadStrategy=normal, ignoreZoomSetting=false, ie.fileUploadDialogTimeout=3000, version=11, platform=WINDOWS, proxy={httpProxy=HOSTNAME:62556, proxyType=manual, sslProxy=HOSTNAME:62556}, nativeEvents=true, ie.ensureCleanSession=true, elementScrollBehavior=0, ie.browserCommandLineSwitches=, requireWindowFocus=false, browserName=internet explorer, initialBrowserUrl=http://localhost:46295/, javascriptEnabled=true, ignoreProtectedModeSettings=false, enableElementCacheCleanup=true, unexpectedAlertBehaviour=dismiss}]

    • Hello,

      Thank you for providing this information about the issue. We have confirmed the problem, and we are working on a solution for a future build of Edge. We are presently tracking this issue as a duplicate of an existing internal bug report. We look forward to additional feedback you may have on how we can improve Microsoft Edge.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in