newbie: can't see WS traffic in Fiddler4

[notreallymeanyway]

I just installed Fiddler4 on Windows 7, and am running Firefox 42.0.  I revised my custom script as in <http://www.codeproject.com/Articles/718660/Debug-Inspect-WebSocket-traffic-with-Fiddler>.  I have set the proxy setting to use the same proxy for all protocols.  I see no WS traffic either with my own code (1000s of 16K binary messages) or with the WS echo test online.   The process associated with other sessions is always avp:5996, which I think may indicate that my antivirus is acting as the proxy rather than Fiddler.  Any help would be appreciated.

[EricLaw]

The AVP process means that AVG is intercepting traffic before Fiddler sees it, which will confuse any process-based filters, but should be otherwise harmless.

Fiddler natively supports WebSockets traffic display without the legacy hacks you see in that CodeProject article; see http://www.telerik.com/blogs/what-s-new-in-fiddler-4-5 for some screenshots. Simply double-click (or hit Enter) on the WebSocket entry in Fiddler's Web Sessions list to make the WebSockets tab appear.

[notreallymeanyway]

Thanks for the tips.  I uninstalled and reinstalled after reading the "what's new" page, and added the onWebSocket function.  When I open a page in IE, I get plenty of output in the session list.  None are marked WS or Websocket:  all are HTTP even when running the echo test.  With Firefox I get no output at all in the sessions list -- does Fiddler4 only work with IE?  I'm getting close!  ... but I need another jolt of advice.

[EricLaw]

Fiddler works with all browsers. Firefox may still have a bug where it tries to use the SOCKS proxy (rather than the HTTPS proxy) for WebSockets.

Can you email me (Help > Send Feedback) a SAZ file of the traffic? The Web Sessions list should look like this: