7 ms·
DevTools -> network -> Change the throttling to "offline"
by avel 5y ago
DevTools -> network -> Change the throttling to "offline"
- 41b696ef1113 5y agoOffline is not an option in Firefox, just progressively worse connection options.
- jacobmischka 5y agoIt's a bit less convenient, but I think you can accomplish the same using a `*` request blocking rule: https://i.imgur.com/SYgAxuW.png https://i.imgur.com/SYgAxuW.png
- treszkai 5y agoThat works, but you need to keep the "Developer tools" frame open. Once it's closed, the blocking is gone. (Try it with an infinity feed.)
- ajsnigrutin 5y agoFile -> work offline?
- TameAntelope 5y agoYou could also just see that no network requests are sent when you type.
- ganafagol 5y agoAnd once you see them, you do what? Rollback reality?
- TameAntelope 5y agoI'm confused. Are you suggesting you should test with "real" data first?
- ganafagol 5y agoI'm suggesting that monitoring an application for malicious behavior to detect it after the fact is the wrong approach. Once the data is sent, it's too late to do anything about it. Oh you first try fake data? That's easy to counter. For example probabilisticly: the app tosses a coin and only sends the data with 50% chance the first time. Now half of people using your approach will think the app is safe and get their data stolen anyway. Or use some side channel, delay activity, ...
- dzhiurgis 5y agoDoes it stay offline if you have a service worker?
- pimterry 5y agoNote that today in Chromium-based browsers this does _not_ take a page completely offline - it only affects some specific internal HTTP request APIs, so it's still quite possible to exfiltrate data. For example, WebSockets & WebRTC aren't affected: https://bugs.chromium.org/p/chromium/issues/detail?id=423246 https://bugs.chromium.org/p/chromium/issues/detail?id=423246 (although it looks like there's work to start to properly support this in progress).