Bad Behavior 2.2.2 has been released. This is a maintenance release and is recommended for all users.
Who Should Update?
MediaWiki and WordPress users, as well as all users who have enabled the Reverse Proxy feature, should update in order to receive the important bug fixes contained in this release.
Users who have not yet updated to the 2.2 series should plan to update as soon as possible. Support for the 2.0 series will end June 30, 2013.
Download
Download Bad Behavior now.
What’s New?
Changes since 2.2.1:
- When a site enabled the Reverse Proxy option when it was not actually needed, Bad Behavior would sometimes fail to acquire the correct IP address for incoming requests. Bad Behavior’s code to detect this situation and acquire the correct IP address has been completely rewritten.
- MediaWiki: The default for the setting $wgBadBehaviorTimer has been reset to false. This setting enables an HTML comment to be inserted into wiki pages with run time information; however this causes blank lines to appear in pages with transcluded content or HTML forms. This code will be revisited in a future release.
- WordPress: A spurious PHP warning was being emitted when Bad Behavior captured a copy of incoming spam that was identified by another plugin. This warning has been removed.
Support
Donate today to ensure that I can keep going in the fight against our mutual enemies, the spammers.
Bad Behavior 2.2.1 has been released. This is a maintenance release and is recommended for all users.
Who Should Update?
All 2.2 series users should update in order to receive the important bug fixes contained in this release.
Users who have not yet updated to the 2.2 series should plan to update as soon as possible. Support for the 2.0 series will end June 30, 2013.
Download
Download Bad Behavior now.
What’s New?
Changes since 2.2.0:
- On platforms where database logging is available, Bad Behavior would sometimes continue to log even when the logging setting was turned off. This has been fixed.
- When a site enabled the Reverse Proxy option when it was not actually needed, Bad Behavior would sometimes fail to acquire the correct IP address for incoming requests. Bad Behavior’s code to detect this situation and acquire the correct IP address has been improved.
- WordPress: When a different anti-spam plugin identifies a request as spam, and Bad Behavior did not, Bad Behavior will now log a copy of that request (if logging is enabled). This is to help facilitate reporting of spam not yet detected by Bad Behavior. WordPress users may view the log by visiting the administrative page Tools » Bad Behavior Log.
- WordPress: To improve compatibility with other plugins, Bad Behavior no longer stores data in PHP sessions while screening requests.
Support
I will skip the usual speech. If you’re reading this you already know how valuable Bad Behavior is. Donate today to ensure that I can keep going in the fight against our mutual enemies, the spammers.