{"id":221,"date":"2006-07-14T20:28:39","date_gmt":"2006-07-14T20:28:39","guid":{"rendered":"http:\/\/neosmart.net\/blog\/archives\/221"},"modified":"2023-01-28T15:53:20","modified_gmt":"2023-01-28T21:53:20","slug":"opera-patch-for-bad-behavior","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/opera-patch-for-bad-behavior\/","title":{"rendered":"Bad Behavior Patch for Opera Users"},"content":{"rendered":"

Bad Behavior<\/a> is an excellent ‘profiling’ plug-in that deters most spam bots and attacks on web-based scripts, especially blogs, wikis, and forums. It uses a very detailed and sophisticated combination of checks and algorithms to create a ‘spammer’s profile’ and if a visitor to your site fits it, it’ll block them.\n<\/p>\n

The algorithm is so good that there are almost no false positives, and together with a decent spam plug-in like Akismet or Spam Karma 2, you’re blog will be forever clean. But it has a problem with Opera. Most builds of Opera trigger a false alarm, leaving your blog reader-less, especially with the release of Opera 9, an excellent browser in all rights, but there is a solution. \n<\/p>\n

    \n
  1. Download and extract Bad Behavior<\/a> <\/li>\n
  2. Open .\/bad-behavior\/common_tests.inc.php <\/li>\n
  3. Comment out the code beginning from line 57 to line 60 (inclusive). It should look like this when you’re done:
    \n
    \/*<br \/>\nif (array_key_exists(&#8216;Te&#8217;, $package[&#8216;headers_mixed&#8217;])) {<br \/>\n if (!preg_match(&#8216;\/\\bTE\\b\/&#8217;, $package[&#8216;headers_mixed&#8217;][&#8216;Connection&#8217;])) {<br \/>\nreturn &#8220;582ec5e4&#8221;;<br \/>\n}<br \/>\n}<br \/>\n*\/<\/pre> <\/li>\n
  4. Save the file, upload the directory to your wp-content\/plugins folder, activate, and enjoy! <\/li>\n<\/ol>\n
    The Technical Stuff<\/strong>\n<\/p>\n
    What we just did is disable “TE Request-Header” checks. TE request-headers are from RFC2616, section 14.39; and although we have no doubt that the authors of this wonderful algorithm had their reasons for including TE request-header checks, and that certain spam bots do indeed employ this particular header-request for TE, as far as we can tell the benefits gained by using such a check are minor.\n<\/p>\n
    You can view the entire RFC here<\/a>. At any rate, it doesn’t matter. Bad Behavior is famous for its excellence and cross compatibility, and lack of false positives, so we feel it should stay that way – without the TE request-header checks. An ideal solution would be to implement this function as a subset of ‘Strict Mode’ which is specially designed to block more illicit traffic, but with the knowledge that it may block some legitimate users.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Bad Behavior is an excellent ‘profiling’ plug-in that deters most spam bots and attacks on web-based scripts, especially blogs, wikis, and forums. It uses a very detailed and sophisticated combination of checks and algorithms to create a ‘spammer’s profile’ and … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[56,59,54],"class_list":["post-221","post","type-post","status-publish","format-standard","hentry","category-software","tag-bugs","tag-opera","tag-wordpress"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t