User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20100101 Firefox/13.0.1 Build ID: 20120614114901 Steps to reproduce: In my Firefox extension I want to listen/receive notifications for Websocket connections similar to how the nsIObserver interface and http-modify-request, http-on-examine-response can be used for HTTP connections. I did try using http-* notifications but they do not get fired for websocket request-response communication. The initial websocket connection is an "upgrade" request on the existing http connection and for that request the http-* notifications are fired. This inital request is purely a connection request,there is no data sent on this request. However, once the http connection is upgraded to a websocket connection there are no further notifications sent as the webpage sends/receives data on the websocket channel. I also tried using the nsITraceableChannel but I do not get notified for the websocket communications Actual results: The extension is not notified about the websocket events. So the extension has no way to kick in as the data is being transmitted on the websocket channel Expected results: As the webpage makes requests/receives responses on the Websocket channel, I want my extension to kick-in. This could be through the "http-*" notifications or a completely new set of notification but the extension needs to be able to get notified of websocket events...

This is a valid feature request and we should implement a set of websocket notifications for addons.

I'm not sure if the right fix here is to provide nsIObserverService events for each send/recv websockets do, or to implement something like nsIHttpActivityObserver. We could also use something similar to nsIProgressEventSink, but that only works for the channel's callbacks, which may not be general enough. We also need this to monitor network traffic in bug 746074 and 746073.