title: Debugging binary websockets frames
body: <p>Packet analyzers like <a href="https://stackoverflow.com/questions/5751495/debugging-websocket-in-google-chrome">Wireshark</a>, and <a href="https://stackoverflow.com/questions/9221018/how-to-view-ws-wss-websocket-request-content-using-firebug-or-other">Fiddler</a> allows for low-level packet dump, and appears to be the recommended way to debug binary websocket frames. Major problems of this approach includes secure websocket layers, complexity, friction in the development process, amongst others.</p>
  
  <p>Other than Wireshark, what <strong>browser native, or extension tools</strong> are available to see at least a hex dump of binary frames exchanged via Websockets?</p>
  
  <p><em>edit: as of Chrome 56.0, only frames of textual websocket connections can be watched (by going debug console (F12) -> Network -> Selecting the websocket connection (to identify: it has 101 HTTP status code) -> Frames panel); binary packets still show up as "binary frame (Opcode 2)</em></p>