3 ms·
> to obfuscate what data they are actually sending to sites. Not exactly a thing with Chrome. You can inspect the full JS heap, dig through the call stack one
by judge2020 5y ago
> to obfuscate what data they are actually sending to sites.
Not exactly a thing with Chrome. You can inspect the full JS heap, dig through the call stack one function at a time, and view exactly what goes in and out of XHRs.
- alyandon 5y agoSure, but if Chrome sends a header with a bunch of opaque identifiers that I can't reasonably map to an interest category then that doesn't really help me much.