sihorton/chrome-rDebug — pull request #1 by ashishnegi (2013-09-11 13:27:13+00:00)
Title: Making a webrequest to chrome to know its web socket debug url

When i start chrome with `chrome --remote-debugging-port=9222 --user-data-dir=C:\CEF\laptop_appjs\appjs\appjs\app\data\content

and then i manually navigate to `localhost:9222/json` i get :

`[ {
"description": "",
"devtoolsFrontendUrl": "/devtools/devtools.html?ws=localhost:9222/devtools/page/E2FF407E-207E-4B88-A3A8-31436E27FC1A",
"faviconUrl": "",
"id": "E2FF407E-207E-4B88-A3A8-31436E27FC1A",
"thumbnailUrl": "/thumb/E2FF407E-207E-4B88-A3A8-31436E27FC1A",
"title": "New Tab",
"type": "page",
"url": "http://localhost:9222/json",
"webSocketDebuggerUrl": "ws://localhost:9222/devtools/page/E2FF407E-207E-4B88-A3A8-31436E27FC1A"
} ]`

This web-socket-debug-url can be different on different machines and at different times.

Hence, a web request is required first to get the url on which this demo example should work.