« New e-mail phishing alert – “It’s Easy, Secure and Free!” in big bold letters | Home | Console-free gtkmm applications in Visual Studio 2008 »
Windows Live and Bad Behaviour plugin incompatiblity
By admin | November 16, 2009
While the Bad Behaviour plugin is an excellent plugin for blocking annoying comment spam and other stuff, but there is a known incompatibility with the Bad Behaviour plugin with the Windows Live. You can go and read the full article, but here is a quick drill-down of what you need to know:
Bad Behaviour Logs
We can't get information for this web activity...
WordPress has been added to your profile...
Basically, the Bad Behaviour plugin for some reason seems to think that the Windows Live “robot” sends a bad User-Agent string, and blocks Windows Live from accessing your recent posts. To remedy this, add “65.54.233.0/24”, after line 19 in <blogpath>/wp-content/bad-behavior/bad-behavior/whitelist.inc.php. It should look like this after you’re done:
<?php if (!defined('BB2_CORE')) die('I said no cheating!');
function bb2_whitelist($package)
{
// DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGER!
// Inappropriate whitelisting WILL expose you to spam, or cause Bad
// Behavior to stop functioning entirely! DO NOT WHITELIST unless you
// are 100% CERTAIN that you should.
// IP address ranges use the CIDR format.
// Includes four examples of whitelisting by IP address and netblock.
$bb2_whitelist_ip_ranges = array(
"64.191.203.34", // Digg whitelisted as of 2.0.12
"208.67.217.130", // Digg whitelisted as of 2.0.12
"10.0.0.0/8",
"172.16.0.0/12",
"192.168.0.0/16",
"65.54.233.0/24",
// "127.0.0.1",
);
// DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGER!
// Inappropriate whitelisting WILL expose you to spam, or cause Bad
// Behavior to stop functioning entirely! DO NOT WHITELIST unless you
// are 100% CERTAIN that you should.
// You should not whitelist search engines by user agent. Use the IP
// netblock for the search engine instead. See http://whois.arin.net/
// to locate the netblocks for an IP.
// User agents are matched by exact match only.
// Includes one example of whitelisting by user agent.
// All are commented out.
$bb2_whitelist_user_agents = array(
// "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) It's me, let me in",
);
// DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGER!
// Inappropriate whitelisting WILL expose you to spam, or cause Bad
// Behavior to stop functioning entirely! DO NOT WHITELIST unless you
// are 100% CERTAIN that you should.
// URLs are matched from the first / after the server name up to,
// but not including, the ? (if any).
// Includes two examples of whitelisting by URL.
$bb2_whitelist_urls = array(
// "/example.php",
// "/openid/server",
);
// DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGER! DANGER!
// Do not edit below this line
if (!empty($bb2_whitelist_ip_ranges)) {
foreach ($bb2_whitelist_ip_ranges as $range) {
if (match_cidr($package['ip'], $range)) return true;
}
}
if (!empty($bb2_whitelist_user_agents)) {
foreach ($bb2_whitelist_user_agents as $user_agent) {
if (!strcmp($package['headers_mixed']['User-Agent'], $user_agent)) return true;
}
}
if (!empty($bb2_whitelist_urls)) {
$request_uri = substr($settings['request_uri'], 0, strpos($settings['request_uri'], "?"));
foreach ($bb2_whitelist_urls as $url) {
if (!strcmp($request_uri, $url)) return true;
}
}
return false;
}
?>
The edit to line 20 is the change required in order to accommodate Windows Live services on your WordPress blog. If you found this article helpful or interesting, please help Compdigitec spread the word. Don’t forget to subscribe to Compdigitec Labs for more interesting articles!
If you found this article helpful or interesting, please help Compdigitec spread the word. Don’t forget to subscribe to Compdigitec Labs for more useful and interesting articles!
Topics: HTTP (Internet) | 1 Comment »
September 14th, 2023 at 20:31
… [Trackback]
[…] There you will find 33571 more Info on that Topic: compdigitec.com/labs/2009/11/16/windows-live-and-bad-behaviour-plugin-incompatiblity/ […]