The Session object, when trying to cache its own Capabilities, calls
GET /session/:sessionId
which isn't part of the W3C-Documentation and so Selenium (or probably chromedriver) fails to recognize that as a W3C command. That being said, new Sessions are initialized (in the webdriver-function "session") by calling
POST /session
and the response contains both the sessionId and the Capabilities of the newly created Session which is then used to create a Session object - except that it doesn't pass on the Capabilities that it already has but instead lets the Session object make a non-W3C command.
The Session object, when trying to cache its own Capabilities, calls
GET /session/:sessionId
which isn't part of the W3C-Documentation and so Selenium (or probably chromedriver) fails to recognize that as a W3C command. That being said, new Sessions are initialized (in the webdriver-function "session") by calling
POST /session
and the response contains both the sessionId and the Capabilities of the newly created Session which is then used to create a Session object - except that it doesn't pass on the Capabilities that it already has but instead lets the Session object make a non-W3C command.
ENV: