iQFLBAABCAA1FiEEzdc6C8U0Fd1W9WC36h3SEMrMxF4FAltoT7YXHG1pdGNoZWxs

 a3JvZ0BnbWFpbC5jb20ACgkQ6h3SEMrMxF4SmQf/cjeFIWzlXzlnQKNoY4sLhDNT
 XR1yWRPHVib6mKLx01MCCDUqH9Qkb0SUbXYsnxjGRVpD/Ap38hCNgkmmVL4F84oo
 GdqcLKONfUETOXi4snZLNj56Fw2d+U4z5QTurx3YiH6qUTvzRBUZevBYXNbYlI/0
 pvOsGmJplG9QVaP1uA5pgcLWgc9sCVSJ4h0hiOsWA4gPlMWXxYcU60cKjLMTYA3J
 Ctk40oF52EeV/NKBsSM2dUT4iJ2ES4Eeuamh9IX3tsKSwUF09EafQHoJZxLPmG6h
 w/qjVMHRKUwzw65Omp+RiT06COBVnCjBhqBXbyXGszKoOz7Zo6iYR0ltiz02pg==
 =9AdF
 -----END PGP SIGNATURE-----

Some Fixes to default include files
- Examples are commented out
- No need for custom bad referrer include REF: #71

bad-referrer-words.conf

@@ -1,4 +1,4 @@
-# EDIT THIS FILE AS YOU LIKE TO ADD OR REMOVE ANY BAD WORDS YOU WANT TO SCAN FOR ###
+# EDIT THIS FILE AS YOU LIKE TO ADD OR REMOVE ANY BAD REFERRERS or BAD WORDS YOU WANT TO SCAN FOR ###
 
 ##############################################################################
 #        ___                 __                                              #
@@ -13,35 +13,58 @@
 ##############################################################################
 
 # This is merely an example and gets auto included as since Version 2.2017.07 introduced on 2017-04-20
-# This file must exist on your system or Nginx will fail a reload due to a missing file
+# This file must exist on your system or Apache will fail a reload due to a missing file
 # For all intensive purpose you can delete everything inside this file and leave it
-# completely blank if you do not want your Nginx Blocker to include scanning for bad words within urls or referrer string
+# completely blank if you do not want your Apache Blocker to include scanning for bad words within urls or referrer string
 # Only add one entry per line
 
-# *******************************
-# !!! WARNING WARNING WARNING !!!
-# *******************************
-
-# ***************************************
-# PLEASE BE VERY CAREFUL HOW YOU USE THIS
-# ***************************************
-# Here is an example of how one supposed bad word can cause your whole site to go down.
-# An issue was logged where the users own domain name was specialisteparquet.com
-# Because this list contained the word "cialis" it was detected within his domain name causing 
-# his entire site to go down and not server any assets.
-# That one entry would even cause any site containing a word like "specialist" anywhere in any
-# of their sites pages to cause them to be blocked and whitelisting your own domain name in the
-# whitelist-domains.conf file will not even bypass this, SO BE CAREFUL PLEASE
-
-SetEnvIfNoCase Referer ~*adultgalls spam_ref
-SetEnvIfNoCase Referer ~*bigblackbooty spam_ref
-SetEnvIfNoCase Referer ~*cookie-law-enforcement spam_ref
-SetEnvIfNoCase Referer ~*free-share-buttons spam_ref
-SetEnvIfNoCase Referer ~*free-social-buttons spam_ref
-SetEnvIfNoCase Referer ~*fuck-paid-share-buttons spam_ref
-SetEnvIfNoCase Referer ~*law-enforcement-bot spam_ref
-SetEnvIfNoCase Referer ~*law-enforcement-check spam_ref
-SetEnvIfNoCase Referer ~*share-buttons-for-free spam_ref
-SetEnvIfNoCase Referer ~*social-buttons- spam_ref
-SetEnvIfNoCase Referer ~*vvakhrin-ws1 spam_ref
-SetEnvIfNoCase Referer ~*xxxrus spam_ref
+# PLEASE NOTE:
+# THIS INCLUDE FILES IS TO BE USED FOR CREATING YOUR OWN CUSTOM SET OF BAD REFERRERS AS WELL AS BAD REFERRER WORD SCANNING
+
+# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
+
+
+	# *************************
+	# CUSTOM BAD REFERRERS HERE
+	# *************************
+
+
+	#SetEnvIfNoCase Referer ~*somebad\.website spam_ref
+	#SetEnvIfNoCase Referer ~*somethingbad\.com spam_ref
+	#SetEnvIfNoCase Referer ~*veryverbad\.com spam_ref
+	#SetEnvIfNoCase Referer ~*superbadwebsite\.com spam_ref
+
+
+
+	# *******************************
+	# CUSTOM BAD REFERRERS WORDS HERE
+	# *******************************
+
+	# *******************************
+	# !!! WARNING WARNING WARNING !!!
+	# *******************************
+
+	# ***************************************
+	# PLEASE BE VERY CAREFUL HOW YOU USE THIS
+	# ***************************************
+
+	# Here is an example of how one supposed bad word can cause your whole site to go down.
+	# An issue was logged where the users own domain name was specialisteparquet.com
+	# Because this list contained the word "cialis" it was detected within his domain name causing 
+	# his entire site to go down and not server any assets.
+	# That one entry would even cause any site containing a word like "specialist" anywhere in any
+	# of their sites pages to cause them to be blocked and whitelisting your own domain name in the
+	# whitelist-domains.conf file will not even bypass this, SO BE CAREFUL PLEASE
+
+	#SetEnvIfNoCase Referer ~*adultgalls spam_ref
+	#SetEnvIfNoCase Referer ~*bigblackbooty spam_ref
+	#SetEnvIfNoCase Referer ~*cookie-law-enforcement spam_ref
+	#SetEnvIfNoCase Referer ~*free-share-buttons spam_ref
+	#SetEnvIfNoCase Referer ~*free-social-buttons spam_ref
+	#SetEnvIfNoCase Referer ~*fuck-paid-share-buttons spam_ref
+	#SetEnvIfNoCase Referer ~*law-enforcement-bot spam_ref
+	#SetEnvIfNoCase Referer ~*law-enforcement-check spam_ref
+	#SetEnvIfNoCase Referer ~*share-buttons-for-free spam_ref
+	#SetEnvIfNoCase Referer ~*social-buttons- spam_ref
+	#SetEnvIfNoCase Referer ~*vvakhrin-ws1 spam_ref
+	#SetEnvIfNoCase Referer ~*xxxrus spam_ref

blacklist-user-agents.conf

@@ -43,16 +43,18 @@
 # the "\b" are word boundaries which prevents partial matching and false positives.
 # Follow the regex formatting examples below.
 
-# *************************
-# BLACKLIST ADDITIONAL BOTS
-# *************************
+# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
 
-BrowserMatchNoCase "^(.*?)(\bMyVeryBadUserAgentName\b)(.*)$" bad_bot
-BrowserMatchNoCase "^(.*?)(\bMy\ Bad\ User\ Agent\b)(.*)$" bad_bot
+	# *************************
+	# BLACKLIST ADDITIONAL BOTS
+	# *************************
 
-# *************************
-# WHITELIST ADDITIONAL BOTS
-# *************************
+	#BrowserMatchNoCase "^(.*?)(\bMyVeryBadUserAgentName\b)(.*)$" bad_bot
+	#BrowserMatchNoCase "^(.*?)(\bMy\ Bad\ User\ Agent\b)(.*)$" bad_bot
 
-BrowserMatchNoCase "^(.*?)(\bMyVeryGoodUserAgentName\b)(.*)$" good_bot
-BrowserMatchNoCase "^(.*?)(\bMy\ Bad\ User\ Agent\b)(.*)$" good_bot
+	# *************************
+	# WHITELIST ADDITIONAL BOTS
+	# *************************
+
+	#BrowserMatchNoCase "^(.*?)(\bMyVeryGoodUserAgentName\b)(.*)$" good_bot
+	#BrowserMatchNoCase "^(.*?)(\bMy\ Bad\ User\ Agent\b)(.*)$" good_bot

whitelist-domains.conf

@@ -21,5 +21,7 @@
 # For example myfirstowndomainname.com should be entered as myfirstowndomainname\.com
 # and my-second-owndomainname.com should be entered as my\-second\-owndomainname\.com
 
-SetEnvIfNoCase Referer ~*yourdomain\.com good_ref
-SetEnvIfNoCase Referer ~*your\-domain\.com good_ref
+# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
+
+	#SetEnvIfNoCase Referer ~*yourdomain\.com good_ref
+	#SetEnvIfNoCase Referer ~*your\-domain\.com good_ref

whitelist-ips.conf

@@ -12,4 +12,9 @@
 #                                                                            #
 ##############################################################################
 
-#Require ip 192.168.1.0 < Your own IP's will go here avoid using 127.0.0.1 to avoid breaking the Blocker
+# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
+
+	#Require ip 192.168.1.0 
+
+
+# DO NOT EVER USE 127.0.0.1 only real public facing IP addresses.