I haven't seen much of a discussion about this and so wanted to make a post. I've noticed some sites will refuse to load at all if they detect any form of ad blocking, which results in a browser-based error of "connection refused" instead of the usual website-based messages you'd usually expect.
After some digging, I see a bit more of how this process works - the site is checking to see if your browser was able to resolve (via DNS) and load content (via browser) from a specific subdomain (usually the ad-content server itself) before it decides to display the content of the page. If it is unable to load the subdomain in question, it refuses your connection completely instead of displaying any content.
A good example of this is Engadget; if your browser can't load "guce.engadget.com" for any reason, the parent domain "engadget.com" will refuse to let you connect at all. In my block logs I can see "Engadget.com" is resolving just fine but the "guce" subdomain is blocked by adblocking, resulting in the above behavior. Once I let "guce" through I can once again access the rest of their domain/website.
Just thought it was interesting and wanted to share.
[link] [comments]
No comments:
Post a Comment