4 ms·

Stupid question: how does it work when the majority of traffic is through SSL, making a request to an ad and a request to actual content indistinguishable? I d

• neoeldex 10y ago
  No such thing as stupid questions, but ads are usually served through a specific domain, which can be blocked, even with SSL
  • kirubakaran 10y ago
    How about this? https://twitter.com/officialjaden/status/329768040235413504?lang=en https://twitter.com/officialjaden/status/329768040235413504?...
• mrstone 10y ago
  As far as I can tell, it doesn't; they don't support blocking SSL traffic. Makes it kind of useless, I think.
  • promofaux 10y ago
    Of course it can! If it has a domain name, it can be blocked. What you may see is the browser grumbling about it. Essentially all that is happening is a client asks for a domain (e.g ssl.google.com) and if it is on the blacklist, then it returns it's own local IP address for that domain instead of the real one. Which is where you will find the browser complaining. All we return is a blank page/blocking information page, but not via https. Of course, we could probably get around that by generating self-signed certificates on install, but the user would then need to install that certificate on all of their client machines (I think, I'm not massively proficient in this area!) which makes it an extra, and not vital, step that may scare off the more novice users.