DragonflyCMS Projects > Audit (IP Tracker) > Can't get rid of Inktomi/Yahoo! > Community Forums > Phoenix Netology
Forum Index > Management > Audit (IP Tracker)

Can't get rid of Inktomi/Yahoo! Reply to topic

I have too many Inktomi/Yahoo! visits!
I entered: $exclude_hosts = array('.+inktomisearch.com','msnbot.msn.com');
It works fine for msn bot, but not for Inktomi!!
I've tried also:$exclude_ips = array('68.142.+','66.196.+');
but it doesn't seems to work either Sad

Any idea?
Thank you Smile

Please enter your server specs in your user profile! 😢

just 'inktomisearch.com'

• Donations & Audit for DragonflyCMS •

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):

I can't seem to get rid of this or other bots either!

I'm using
$exclude_hosts = array('inktomisearch.com', 'msnbot.msn.com', 'googlebot.com');

But this still isnt blocking bots such as:

crawl-66-249-71-67.googlebot.com
crawl-66-249-64-33.googlebot.com
lj2225.inktomisearch.com
crawl-66-249-64-39.googlebot.com
lj2545.inktomisearch.com


I've tried several variations of the inktomisearch with wildcards, but I can't seem to get it to work Confused

Please enter your server specs in your user profile! 😢

hmm, still not sure why that isn't working, so I've restructured the check - it should now detect host names and ip addresses - follow existing instructions in ipconfig.php for excclusion of IP and hostname.

'inktomisearch.com' is sufficient to ensure it is excluded. Some care needs to be taken now e.g. if you were to use 'msn.com', it would exclude all things msn, including search queries, so it is important to use something like 'msnbot.msn.com'.

Simply extract the iptracking.inc from the attached zip and upload to modules/IP_Tracker
Attachment: iptracking.inc.zip
Description
Filename iptracking.inc.zip
Filesize 1.09 KiB
Downloaded 3 Time(s)
You are not allowed to view/download this attachment

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):

Something I should have thought of originally was to just provide a flag that automatically excludes known search engines - that way you don't have to keep adding IPs and hostnames for bots that Dragonfly already identifies.

That way, you have the main ones covered and just use ipconfig to cover the gaps and any other specifics you want to handle.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):

Phoenix wrote
Something I should have thought of originally was to just provide a flag that automatically excludes known search engines - that way you don't have to keep adding IPs and hostnames for bots that Dragonfly already identifies.

That way, you have the main ones covered and just use ipconfig to cover the gaps and any other specifics you want to handle.


That would be a good addition Smile

Thanks for the new file, I'll let you know if there's any problems!

Please enter your server specs in your user profile! 😢

new flag $exclude_bots now introduced - works fine and will be in next version - just doing some further testing on unix time changes.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):

all done and tested okay - simply activate the flag in ipconfig

nukebiz.com/Downloads/...id=37.html

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):

A few other suggestions that could be good.

Can you exclude certain users? e.g. myself on my own site racks up a tonne of logging that doesn't need doing.

And maybe a button to clear all data from the table in the Module? Or maybe only for specific entries?

Please enter your server specs in your user profile! 😢

exclude users can be added in an array like the others, though eventually I have to create a proper admin interface.

With an admin interface, it would be fairly straight forward to allow deletion of the first x,000 records, which essentially is what the program does now by setting the $ipdel variable.

Specific entries is a bit more work because you really need to know what you want before you do it.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):

oh well, started it - IP Tracker config now runs mainly from a new database table, though it means an extra database query, which was the benefit of a static config file.

Still some exclusion arrays to work out how to manage, and the admin interface, although the admin is the easy part.

Server specs (Server OS / Apache / MySQL / PHP / DragonflyCMS):

Well good luck, with the testing - If I can help at all, let me know! Smile

Please enter your server specs in your user profile! 😢

All times are Australia/Adelaide


Jump to:

Terms of Use : Phoenix Netology : © 2004 - 2021
Interactive software released under GNU GPL, Code Credits, Privacy Policy