UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce the problem:
Here's what a typical start of a websocket session looks like

creating ws://localhost:9229/node
> {"id":1,"method":"Runtime.enable"}
> {"id":2,"method":"Debugger.enable"}
> {"id":3,"method":"Console.enable"}
> {"id":4,"method":"Profiler.enable"}
> {"id":5,"method":"HeapProfiler.enable"}
> {"id":6,"method":"Runtime.run"}
< {"method":"Runtime.executionContextCreated","params":{"context":{"id":1.000000,"isDefault":true,"origin":"","name":"NodeJS Main Context","frameId":""}}}
< {"id":1.000000,"result":{}}
< {"id":2.000000,"result":{}}
< {"error":{"code":-32601.000000,"message":"'Console.enable' wasn't found"},"id":3.000000}
< {"id":4.000000,"result":{}}
< {"id":5.000000,"result":{}}
< {"id":6.000000,"result":{}}
< {"method":"Debugger.scriptParsed","params":{"scriptId":"39","url":"bootstrap_node.js","startLine":0.000000,"startColumn":0.000000,"endLine":457.000000,"endColumn":0.000000,"executionContextId":1.000000,"hash":"D0A4F4210878862AC73FFB6658F7EC021A33D3F4","isContentScript":false,"isInternalScript":false,"isLiveEdit":false,"sourceMapURL":"","hasSourceURL":false,"deprecatedCommentWasUsed":false}}

What is the expected behavior?
Console.enable should not error since console is in the js_protocol.json domain

What went wrong?
< {"error":{"code":-32601.000000,"message":"'Console.enable' wasn't found"},"id":3.000000}

Did this work before? N/A 

Chrome version: 51.0.2704.103  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0