As you would not be able to discern the nature of that content without looking it, potentially loading additional resources, there doesn't seem to be a good way to identify "bad" content here. On certain sites the noscript tag could contain valuable information for you. This would probably the most secure option but also the most complex. Fork your favorite browser and modify it not to evaluate the noscript part.The following question could be helpful with this: how to run greasemonkey script before the page content is displayed? Depending on when this script is loaded it might be too late and your browser might try to pre-cache it as well. Use something like a GreaseMonkey script or similar to modify the DOM and remove the noscript part.This won't protect you from tracking pixels that are delivered from the same domain you're visiting though. You could e.g use RequestPolicy and set the scope accordingly. You already seem to be aware of a tool-set that could do that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |