I have error in log file:
[Fri Oct 11 00:47:03 2013] [alert] /home/www/.htaccess: RewriteCond: cannot compile regular expression '^(|-?)$'\n
Plugin Author
AITpro
(@aitpro)
hmm interesting, which web host do you have? I have seen a few hosts with mod_security installed that will not process the question mark in this type of format/condition.
The simple solution is just to copy this Brute Force Login Protection code to BPS Custom Code and then comment that line of code out. That particular condition handles blank spambot user agents. it is not that critical to include.
Plugin Author
AITpro
(@aitpro)
Probably you can just change the rule to this and it will work.
RewriteCond %{HTTP_USER_AGENT} ^$ [NC,OR]
Plugin Author
AITpro
(@aitpro)
Ok we will change this rule permanently in the next version of BPS so that it will work in the widest possible range of environments. This will not affect anyone who has already manually changed the code or added this code to BPS Custom Code and modified it to make it work. In other words, we will add a check to see if the code modification has already been done. Thanks.
If I might jump in here, could the above possibly have anything to do with why my two add-on domains at BlueHost each redirected (once) away from admin to install after the BPS upgrade?
Plugin Author
AITpro
(@aitpro)
Nope, that sounds like the Broken cPanel HotLink Protection tool problem.
I just took a look and my BlueHost cPanel shows that tool disabled, and then it showed an error (inability to write to htaccess) after I had cleared its editor of all code and tried to save it empty. I have yet to ever try the BPS version of HotLink Protection, but I have been thinking about doing that.
Same problem here. After the BPS update the website stopped working. The only solution was to manually delete the .htaccess file.
The hosting is IXWebHosting.
Please when you fix this problem do mention the fix in update changelog, till then the plugin will stay disabled.
Good luck.
Plugin Author
AITpro
(@aitpro)
Enable and Disable is also broken – you cannot disable the HotLink Protection Tool. There is only one way to prevent it from malfunctioning – lock your root .htaccess file so that it cannot wipe out your root .htaccess file code. It sounds like you already have locked your root .htaccess file with 404 Read-Only permissions.
So far the only issue that is occuring on a global level is that Host’s that have mod_security installed are having issues with the question mark condition. We will try to get an update out ASAP.
Change this:
RewriteCond %{HTTP_USER_AGENT} ^(|-?)$ [NC,OR]
To this:
RewriteCond %{HTTP_USER_AGENT} ^-?$ [NC,OR]
They do the same thing, except the second way is the most efficient way.
Plugin Author
AITpro
(@aitpro)
Actually the problem is the question mark itself. We were already aware of this issue with mod_security, but on the final phase of release the note was missed. 😉
Plugin Author
AITpro
(@aitpro)
Yep, but there is still another issue that occurs when mod_security has certain SecRules/SecFilters in place so in order to make the code have the widest possible range of compatibility we will be going with this code.
RewriteCond %{HTTP_USER_AGENT} ^$ [OR]
