mod_antibot bug in Helicon Api version 3.1.0.248

[VinceOmega Profile]

Some colleagues of mine and myself have discovered a bug within this particular version of Helicon Ape. When you turn on mod_antibot and enable antibot conditions and rules for your site Helicon Ape will continuously log entries for mod_antibot in it's program files folder (i.e. C:\Program Files (x86)\Helicon\Ape\logs). It would continue to write there even if you didn't have any logging feature turned on (including the default logging for helicon ape.) Once we upgraded to the latest version of Helicon Ape, this problem stopped.

In order to arrive to that conclusion we had to test this theory on three different machines (ruling out different edges before updating that machine with the latest version, and then testing it afterwards.) before we could implement the fix to our production environment. This was a huge problem for our production environment because unbeknownst to us, the continuous logging created a 30 GB log file, taking up close to 50% of our hard drive space. It halted our production environment and cost a day of work as we tried to discover what the issue was.

This could have been avoided if there was an updated release note log on the site. Hopefully someone will find this post useful.

TL;DR : If you have v3.1.0.248 and plan on using mod_antibot, update to 3.1.0.256 first. Save yourself some trouble.

[Yaroslav]

Hello.

I am genuinely sorry for the inconvenience. Indeed mod_antibot was considered experimental feature and logging was on by default. Starting from build 256 this was fixed and logging is now controlled by AntibotLog directive. Again sorry for all the troubles it caused.
I will update release history tomorrow.