Give the thieves a good kick in the butt!

Version: 11.1
Revision: 33 Build 12

Give the thieves a good kick in the butt!

For the passed months, I was reading a book about “Linux coding”. It really made me wanting to simplify the ‘htaccess’ by modifying parts of my blocking sequences. So that the server doesn’t get angry and overkill the resources. However, this source will only support ‘Linux’ servers with HTA backbone support.

1.] Create a new ‘HTA script file’ and copy these codes…

RewriteCond %(HTTP_REFERER) !^http(s)?://(www\.)?your-domain\.com [NC]
RewriteCond %(HTTP_REFERER) !^$
RewriteCond %(HTTP_REFERER) ^http(s)?://.*$
RewriteRule \.(jpe?g|gif|png|bmp)$ - [F]

2.] Save your new ‘HTA file’ and delete your old revision. Nevertheless, if you want to keep your old file, you will need to rename it as ‘old.htaccess’ or something like that.

3.] Upload your new ‘htaccess’ file and delete your internet temporary files.

4.] You are done!

Tips for confused users

‘nocase | NC’ [no case] – this source makes the test case-insensitive. In other terms, there is no similarity or difference between ‘upper-cases and lower-cases’. This flag is effective only for comparison, and it has no direct – effect on file systems and sub-request checks.

‘ornext | OR’ [or next condition] – this source is useful if you want to link or combine individual rules with a local OR instead of the using AND.

‘forbidden | F’ (force URL to be forbidden) – this source forces the Url to be forbidden for all users. So, if you ever add one of these commands, there is going to be a 403 (FORBIDDEN) message right at your door.

‘^’ – this is the start of line anchoring.
‘$’ – this is the end of line anchoring

Copyrighted By Lair360

Comments are closed.