Version: 1.00, by calorie
Developer Last Online: Nov 2023
Version: 3.0.3
Rating:
Released: 09-29-2004
Last Update: Never
Installs: 16
No support by the author.
Hack 1: vB303_remove_bot_sids_1.txt
Okay so I notice that there are some bots where SIDs are in the requests. One such bot is msnbot, and who knows of the current code behind this bot, but it seems that it treats each different SID as a new link. Here is a quick and dirty hack to prevent this. You need the $_SERVER['HTTP_USER_AGENT'] and $_SERVER['REQUEST_URI'] array elements or their equivalents to use this mini hack. The first step of the hack prevents SIDs in new requests. The second step forces a redirect in order to strip the SIDs from links in the bot memory. There is no need to apply this hack for bots that have google or slurp@inktomi or yahoo! slurp as part of their user agent. Like I said, it is a quick and dirty hack, but it does what I need it to do. If you use this mod, a click of the install button is appreciated.
Hack 2: vB303_remove_bot_sids_2.txt
Do the following to see a list of bots that may appear on the Who's Online list: AdminCP >> vBulletin Options >> Who's Online Options >> Spider Identification Strings & Enable Spider Display & Spider Identification Description
However, according to http://www.vbulletin.com/forum/showthread.php?t=112022, the user agents that don't receive session IDs are hard coded in the sessions.php file. The bots that are hard coded are as follows: google, slurp@inktomi, yahoo! slurp
Thus the bots for the "who's online list" versus the bots in the "remove SID list" are currently not the same. This hack removes the session ids from the list of bots in the vBulletin Options rather than from those that were hard coded in the script.
It may be the case that pages were already crawled by a bot not hard coded in the "remove SID list" so those bots may spider with session ids in the requests. This hack includes an optional step to remove session ids from such bots via redirect.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Here is just one example where a bot indexed a thread, before vB 3.0.6 was released, and still remembers the SID even though reindexing a vB 3.0.7 board:
Note how the first request has a SID in the request, and note how it is 301 redirected, hence the second request. Do tail -f on your access log and watch.