4dsply.com pop behinds
December 14, 2014 6:09 PM
Starting a couple of months ago, some of my favorite web sites started producing pop-behinds that tried to load advertising from 4dsply.com. I've got that URL blocked now, so the pop-behinds come up empty. But they're still happening. It's obvious they're coming from an included Javascript file hosted somewhere else, but I haven't been able to figure out which one it is. Does anyone know who is perpetrating this atrocity?
If you can't tell me that, then how about this? What javascript string can I look for that pushes a window to the rear? If I have that, I can use WinGrep to search all the code for one of these web pages and figure out which is the one I hate.
If you can't tell me that, then how about this? What javascript string can I look for that pushes a window to the rear? If I have that, I can use WinGrep to search all the code for one of these web pages and figure out which is the one I hate.
If that were the case it would happen at a lot more sites than it does. It's not a general problem, it only happens at two specific sites.
posted by Chocolate Pickle at 6:36 PM on December 14, 2014
posted by Chocolate Pickle at 6:36 PM on December 14, 2014
Do you have AdBlockPlus installed? If so, you can do a "show all blockable items" and see a list of all the scripts running on the page. I've blocked oodles of annoying pop-ups/unders this way. It's usually pretty easy to figure out the culprit.
posted by Thorzdad at 6:52 PM on December 14, 2014
posted by Thorzdad at 6:52 PM on December 14, 2014
For Firefox/Iceweasel you can use either or both (I use both) RequestPolicy and NoScript to fine tune which sources a page is allowed to load. You can permanently whitelist ones you know are good, and everything else will be blocked. Works great, if a little fiddly for setup at first.
posted by rhizome at 11:04 PM on December 14, 2014
posted by rhizome at 11:04 PM on December 14, 2014
I'd do a search for the sites url in the source code to find the script that's causing the the window to pop up and work outwards from there, rather than trying to find a string of unknown code that makes a window popup. Another thing you might consider adding to the arsenal is FireBug for Firefox which lets you look at the source code by element.
posted by redindiaink at 5:54 AM on December 15, 2014
posted by redindiaink at 5:54 AM on December 15, 2014
In case anyone's interested, the dirty file was named "3_9.js" and it came from "a.intgr.net", which is now in my blocklist.
posted by Chocolate Pickle at 4:10 PM on December 17, 2014
posted by Chocolate Pickle at 4:10 PM on December 17, 2014
This thread is closed to new comments.
posted by Alterscape at 6:32 PM on December 14, 2014