4 ms·
I just tested the front page of wired.com with this new page I just assembled to quickly check what blockers are not blocking: http://raymondhill.net/httpsb/har
by gorhill 13y ago
I just tested the front page of wired.com with this new page I just assembled to quickly check what blockers are not blocking: http://raymondhill.net/httpsb/har-parser.html http://raymondhill.net/httpsb/har-parser.html.
Despite "Adobe tag" marked as blocked by Disconnect, these requests were not blocked:
http://p.typekit.net/p.gif?a=219379&f=175.10294.10295.10296.10297.14394.14395.14396.14397.14441.14442.15347.15348.15349.15350.15351.15352&h=www.wired.com&ht=sh&k=ztc8lol&s=1&_=1386775967544 http://p.typekit.net/p.gif?a=219379&f=175.10294.10295.10296....
http://www.adobetag.com/d1/condenast/live/Wired.js http://www.adobetag.com/d1/condenast/live/Wired.js
This is the part that bothers me: fooling people into thinking they are shielded against this kind of thing. That is not ok. I accept bugs can happen, but so far your position has been to rationalize why these 3rd-party domains are not blocked.
Oh and in this particular case, Ghostery blocked everything it said it blocked.