How to block the execution of a crooked plugin for Google Chrome?

Question

JavaScript

I ran into a problem, the www.complitly.com/ plugin in chrome constantly knocks on the server at site.com/undefined, which creates an extra load on the server.
How can the site (namely the site, not the server) block this plugin? I tried to redefine its functions in JS, but in vain ...

Answer 1

You can hang a content-dependent hook on the String prototype function.
The plugin uses this construction somestring.replace(/^[^\?]+(\?)*/, '');for some of its purposes
. We can rewrite String.prototype.replaceand, depending on the arguments, throw an exception that is unexpected for it (thus interrupting the plugin at the very beginning).

(function (){
    var realStringPrototypeReplace = String.prototype.replace;
    
    String.prototype.replace = function (what) {
        if (what.toString() === "/^[^\\?]+(\\?)*/") {
            throw new TypeError();
        } else {
            return realStringPrototypeReplace.apply(this, arguments);
        }
    };
}());

The problem here is that the arguments are unique (so that something useful does not run into our trap) and most importantly, that this code starts before the plugin code, otherwise you will have to look for some similar dynamic place.

Answer 2

Not a plugin, but an extension. And don't you think that the very idea that you can block a browser extension through a website is absurd? That's something users of some AdBlock would be constantly surprised.

Answer 3

If we are talking about the fact that this plugin constantly goes to some URL, then this can be a normal solution for a search system with autocomplete, which this system is.
So what do you still want, I do not understand?
… which puts extra load on the server .
What other server is causing the load? Is the plugin constantly trying to access the server you own by url? I do not understand.
How can the site (namely the site, not the server) block this plugin?
What is the difference between a site and a server in your terminology?

Answer 4

create an undefined file and send it through nginx, it will not take a lot of resources to return the void (as I understand you, the 404 handler starts, writes logs and eats kittens)
or something like this
location = /undefined { return 200; }