skype browser version is not measured about carbonalyser HOT 5 OPEN

it is because skype use websockets for videocalls, and web sockets are 0 length when received.

at the time this is not possible from a webextension point of view.

but maybe in the future it could be :

• make a devtools integration of the carbonalyser.
  
• extract websockets information from HAR specification.
  
  note that this information is not currently included in HAR: https://bugzilla.mozilla.org/show_bug.cgi?id=1575465.
  

You should close this issue and we reopen it later when things have moved on browser builder side.

Edit: Even with that things are not perfect because you have to let devtools open while browsing to keep getting HAR infos.

from carbonalyser.

it is because skype use websockets for videocalls, and web sockets are 0 length when received. at the time this is not possible from a webextension point of view. but maybe in the future it could be :

• make a devtools integration of the carbonalyser.
• extract websockets information from HAR specification.
  note that this information is not currently included in HAR: https://bugzilla.mozilla.org/show_bug.cgi?id=1575465.

You should close this issue and we reopen it later when things have moved on browser builder side.

Edit: Even with that things are not perfect because you have to let devtools open while browsing to keep getting HAR infos.

what do you mean by 0 length when received? The web extension does not process the received frames? I was checking this and it doesn't say anything about 0 length anywhere; there should be a payload.

from carbonalyser.

There is a "payload" (http headers that indicate web socket connexion). But the content length of http request is 0 length (web sockets content by nature is received not all at once). So the "payload": the actual content of websocket communication is received but is not accessible from a web extension point of view.

In that issue we do not talk about what is the reality of websockets but what is possible to do with current state of technology (so only implementation, if you prefer what browser vendor allow us to do).

Maybe you should try to make a first web extension on the subject to really understand how it works "in practice" (if you got the time of course).

from carbonalyser.

There is a "payload" (http headers that indicate web socket connexion). But the content length of http request is 0 length (web sockets content by nature is received not all at once). So the "payload": the actual content of websocket communication is received but is not accessible from a web extension point of view. In that issue we do not talk about what is the reality of websockets but what is possible to do with current state of technology (so only implementation, if you prefer what browser vendor allow us to do). Maybe you should try to make a first web extension on the subject to really understand how it works "in practice" (if you got the time of course).

Zoom did work! :) I guess Zoom doesn't use websockets, right?

from carbonalyser.

zoom use also websockets, so websockets traffic will not be watched.
If you see any increase in the amount of data that pass throught analyzer, it's other request emitted by skype browser version platform.

from carbonalyser.