This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24832 - Remote end MUST listen on both local and remote network interfaces
Summary: Remote end MUST listen on both local and remote network interfaces
Status: RESOLVED INVALID
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency treegraph
 
Reported: 2014-02-26 23:33 UTC by seva
Modified: 2016-09-19 16:12 UTC (History)
4 users (show)

See Also:


Attachments

Description seva 2014-02-26 23:33:33 UTC
It is unspecified whether the 'remote end' MUST/SHOULD/MAY/MUST NOT/... accept commands from a remote 'local end'.

Note: I believe currently IEDriver does not accept commands from remote clients. There is not even a command line switch to enable that.

'Remote end' is defined here:
https://dvcs.w3.org/hg/webdriver/raw-file/default/webdriver-spec.html#naming-the-two-sides-of-the-api

It says "The implementation of the remote end may be on a machine remote from the user of the local end." but that does not require anyone do anything and doesn't even explicitly inform that 'remote end *may* be on the *same* machine where the local end is' (which a formalist-ass like myself may want to see).
Comment 1 Andreas Tolfsen 2015-10-26 01:19:35 UTC
The F2F decided to make the text non-normative.  We should not be using normative language in the appendix.
Comment 2 Simon Stewart 2016-09-02 20:49:28 UTC
I've raised https://github.com/w3c/webdriver/pull/324 to address this.