This interface is provided by your network card. Why is this a problem? Because Wireshark needs a network interface to capture packets from. First Problem: Localhost doesn’t have a network interface For WebSockets work, it seems I’m going to have to bite the bullet.
This is not a reflection of the software, but of my impatience in getting to know enough of it to be usable. Although I’ve come across this network packet analyser before, I’d always quickly given up on it. It doesn’t take much googling of this problem before you are told to go and use Wireshark. Although some support is present - from what I can tell, you can only see the headers, not the stream. I use Fiddler extensively when developing web apps, but it is no use for WebSockets - at least not at the moment. To add to the frustration, there is no easy way to examine the TCP data of the WebSocket stream. My success has been limited to say the least. I’ve been attempting to get some WebSockets code to work using SuperWebSockets and a simple html + javascript page in Chrome. Attempting to use Wireshark to debug WebSockets traffic
0 kommentar(er)
