Mitchell Krog

Daily monitoring of your logs and continually adding new bad referrers That's how this was built. Feel free to also contribute known bad scrapers and referrers to the project.

> Hi Mitchell Is there a better way to block ASN ? Currently I have been blocking all the ip ranges which is in ASN. Post your current IP blocks...

Thanks for your PR @duzun introducing a new include and mapping can and will break many installations out there who update and have a missing include file. Multiple include files...

ah ok I get you, I'll have to think about how we could do this without breaking anything. Using the existing include files could work.

Really not sure with GA4 will have to look when I have time.

Most people do not want these, neither do I, which was the purpose of the blocker from the onset. Simply whitelist any User-Agents & Referrers in the relevant files that...

Us the `bad-referrer-words.conf` file for this

> i have tried code: > > ``` > "~*(?:\b)searchphrase(?:\b)" 1; > ``` > > and in file /etc/nginx/conf.d/globalblacklist.conf i have changed: > > ``` > map $http_user_agent $bad_bot {...

> searchphrase= In your main location / block you need to nest this phrase ``` location / { ..... do stuff ..... location ~ /searchphrase= { return 444; } }...

> works fine in nginx site config: > > ``` > if ($request_uri ~* (searchphrase|searchword) ){ > return 404; > } > ``` great, I'll have to add this kind...