Bad Behavior 2.0.12
January 18th, 2008 by Michael Hampton
Bad Behavior 2.0.12 has been released. It is a maintenance release and is recommended for all users.
Who should upgrade?
All users who use the digg.com social bookmarking service should upgrade to ensure that Bad Behavior-protected pages can be submitted to the service.
Users of Akamai Dynamic Site Accelerator, Dynamic Site Accelerator Enterprise and Web Application Accelerator should upgrade. (I only know of one such user, and I e-mailed you already. If you use these services, and I didn’t e-mail you, please e-mail me.)
What’s new?
New in this release (since 2.0.11):
- IP addresses for the digg.com service have been added to Bad Behavior’s internal whitelist. Upon submitting a story to digg.com, it attempts to load the submitted URL using the PEAR HTTP_Request class, but with a fake HTTP user agent, causing Bad Behavior to block the requests. This problem was reported to digg and the company has failed to respond or to resolve the problem. The IP addresses have been whitelisted due to user demand. If you use digg, please let them know that this is not acceptable to you.
- Users deploying Bad Behavior with Akamai Dynamic Site Accelerator, Dynamic Site Accelerator Enterprise, or Web Application Accelerator found that Internet Explorer users were being blocked by Bad Behavior. This issue was traced to Akamai’s use of the HTTP/1.1 transfer coding feature in its proxy servers. This issue has been fixed.
Download
Support
If you find Bad Behavior useful, please consider making a financial contribution to its further development.
David Cohen Says
Hey Michael, thanks for the new release. I’m getting a 404 when going to download the Zip file.
Jan 18th, 2008 at 9:44 pm
Sean Says
@David: go to http://wordpress.org/extend/plugins/bad-behavior/ to download it.
Jan 18th, 2008 at 10:00 pm
Michael Hampton Says
Ha, you’re right, it was missing. I’ve restored the file.
Jan 18th, 2008 at 10:16 pm
Michael Hampton Says
Let’s not, please. I have enough work already!
Jan 18th, 2008 at 10:17 pm
Sean Says
@Michael: Only reason I suggested that alternative link was because the new WordPress plugin updater in the Dashboard said that was the link for the download.
Jan 18th, 2008 at 11:11 pm
Farmer Says
Thanks for the digg update! (minus my bad behavior)
Jan 19th, 2008 at 7:04 am
Ped Xing Says
Bad Behavior is still not playing nicely with WordPress 2.3. The old wfquery problem remains, even though I posted a fix over six months ago. Now the 2.0.12 version kills 2.3.2 by not giving a return value in bb2_mediawiki_timer somwehere. I’ve had to shut BB off on both my Wikis and I’m worried…
Here’s the backtrace:
Detected bug in an extension! Hook bb2_mediawiki_timer failed to return a value; should return true to continue hook processing or false to abort.
Backtrace:
#0 includes/Parser.php(386): wfRunHooks()
#1 includes/Article.php(3017): Parser->parse(‘ParserAfterTidy’, Array)
#2 includes/Article.php(831): Article->outputWikiText(‘:”Note: This W…’, Object(Title), Object(ParserOptions), true, true, 4453)
#3 includes/Wiki.php(383): Article->view(‘:”Note: This W…’)
#4 includes/Wiki.php(48): MediaWiki->performAction()
#5 index.php(89): MediaWiki->initialize(Object(OutputPage), Object(Article), Object(Title), Object(User), Object(WebRequest))
#6 {main}
Jan 22nd, 2008 at 5:43 pm
Michael Hampton Says
Damn, you’re right about it failing on MediaWiki again. I don’t know how my changes disappeared, because I’m quite sure I incorporated that fix.
But what trouble are you having with WordPress?
Jan 22nd, 2008 at 5:50 pm
Sean Says
@Michael: The WordPress plugin dashboard is saying there is a 2.0.13 version available but your download page still shows 2.0.12. can you confirm or deny? Thanks in advance.
Jan 22nd, 2008 at 9:05 pm
Michael Hampton Says
It will be available sooner or later, but not now. The WordPress plugin auto-update system is stupid and buggy. In any case, the upcoming release has no changes for WordPress so you don’t need to bother.
Jan 22nd, 2008 at 9:34 pm
eti Says
Congrats, very nice, spam comment went down to 1% after installing the plugin.
Jan 23rd, 2008 at 11:22 am
NilsK Says
Are there any plans to make this available for Serendipity?
Jan 24th, 2008 at 4:15 pm
Scott Says
Michael,
Just wanted to say thank you very much for creating Bad Behaviour, its a fantastic tool and I really appreciate it.
You may want to consider adding a couple more IPs to the whitelist. I was implementing a site with PayPal’s IPN recently and noticed that any connections made by PayPal were being blocked by BB. Drop me an email if you want the IP addresses.
Jan 25th, 2008 at 6:35 pm
Kristin K. Wangen Says
I’ve had trouble with trackbacks on WordPress 2.3.x as well, but then I found that “WordPress” was on the blacklist, and by removing that, the trackbacks started to work again.
Is there a reason why WordPress is on the blacklist?
Jan 27th, 2008 at 11:51 am
Boris Says
It’s been some days now since 2.0.12 … has anybody noticed that BB 2.0.12 for Wordpress completely blocks Pingbacks from other Wordpress Blogs because of the User-Agent? (Key 17f4e8c8, User Agent: WordPress/… any number)
Jan 27th, 2008 at 6:40 pm
Michael Hampton Says
Yes, I noticed.
Jan 27th, 2008 at 10:43 pm
Kirk M Says
I would have left this on your post about BB 2.0.13 but comments seem to be closed.
As a longtime user of Windows Live Writer (WLW) and once again using Bad Behavior (I used it previously up to 2.0.11 and those past versions exhibited the same problem with blocking WLW), is there any possible way now to make Bad Behavior compatible with WLW out “of the box” instead of having to either add your own IP to the white list (since the IP can change occasionally) or trying various home grown hacks to Bad Behavior’s files in order to have Bad Behavior allow WLW to work properly? (I add my own IP rather than try any hack actually)
Windows Live Writer is the blog editor of choice now for many WordPress bloggers so it would be great if compatibility could be added to your plugin.
Feb 12th, 2008 at 8:00 pm