4 ms·
Running it on Firefox with web inspector opened, I saw no network traffic at all after the page loaded, so it wasn't sending the network name or password anywhe
by unwiredben 5y ago
Running it on Firefox with web inspector opened, I saw no network traffic at all after the page loaded, so it wasn't sending the network name or password anywhere off my device.
- gruez 5y agoThis method picks up "most" requests, but not all. eg. websocket and webrtc can be used to exfiltrate data but it won't show up on inspector.
- kroltan 5y agoThey do show up, not the connections themselves, but the initiation, no?? At least I always see lots of 101 Switching Protocols responses on sites that use websocket, it might be some sort of nonstandard gateway though. Never used it so dunno. Of course even if that's the case, you gotta load the website with the network inspector already open, to see the initiation.
- switz 5y agoYou can "hide" a websocket connection behind a shared worker and that won't show up in the network connection tab. I do that on a site of mine, but for a less nefarious reason: sharing a websocket connection between multiple tabs.