Block / timeout IP after x 404 errors

Yes, that is very common (hacker/spammer probing/scanning/recon) and goes on all day, every day and will go on until the end of time. You do not have to do anything about this type of stuff (hacker/spammer probing/scanning/recon) since it does not hurt your website/server, SEO, performance or anything else in any significant way. We have looked at/researched if this type of feature would be useful and decided it is not worth the effort required to create since these very common (hacker/spammer probing/scanning/recon) methods do not affect anything negatively.

It mucks up my logs and is a time killer. That is what is the negative in not being able to block them.

Well you can block by the Request URI|URL, but that could also be a time consuming thing to do.

Example:
fckeditor is a very common hacker/spammer random probe/recon URI. So you could add redirect code and redirect that Request URI to the BPS 403 logging template using code like this below in BPS Custom Code in the bottom text box.

RedirectMatch 403 ^/(fckeditor|some-other-URI|another-URI)$
RedirectMatch 403 ^/fckeditor(.*)$

Other examples:
https://stackoverflow.com/questions/9796687/redirectmatch-403-need-to-have-an-exception-for-1-url-in-htaccess
https://stackoverflow.com/questions/22769790/redirect-all-apache-2-2-403-forbidden-to-404-not-found

Assuming all questions have been answered – the thread has been resolved. If you have additional questions about this specific thread topic then you can post them at any time. We still receive email notifications when threads have been resolved.

Thread Start Date: 2-27-2016 to 2-28-2016
Thread Resolved/Current Date: 3-2-2016