8

I would like to create a Chrome Developer Tools extension (a new panel) to analyze WebSockets frames on our own websites. As far as I understand, http://developer.chrome.com/extensions/devtools.network.html is not complete enough to give access to WebSockets frames. What are my best options then?

Thanks!

Thomas
  • 1,360
  • 1
  • 9
  • 15
  • Fiddler is easier to use for debugging websocket. I have recently written an article on CodeProject, which show you how to debug/inspect WebSocket traffic with Fiddler. http://www.codeproject.com/Articles/718660/Debug-Inspect-WebSocket-traffic-with-Fiddler – engineforce Jan 31 '14 at 21:33
  • I needed to inspect WebSocket frames - and came across this Google Chrome extension. https://chrome.google.com/webstore/detail/websocket-frame-inspector/nlajeopfbepekemjhkjcbbnencojpaae Note: I could also install it on Microsoft Edge (Chromium) pretty seamlessly. – kotpal Aug 28 '20 at 03:06

1 Answers1

1

In my personal experience, it is impossible to modify the browser behavior in Chrome, if the addon api does not allow for it - in firefox this is much easier to change as much of the interface logic is written in Javascript, and there are api's for just about anything.

Chrome does support the NPAPI api, however this is written in C++, and the documentation is (best) maintained by Mozilla.

Basically:

Your other option is to checkout the source code of Chrome, and attempt to understand it, modify it, and (possibly) get your changes committed back into the tree.

You might be able to get away with just this https://developers.google.com/chrome-developer-tools/docs/contributing

However, again, you are creating a debug version of Chrome.

In summary, there are no easy answers.

smaudet
  • 609
  • 8
  • 17