In October I posted http://www.icdevgroup.org/pipermail/interchange-users/2004-October/041215.html explaining what I thought was a bug which can result in *permanently* blocked access to Interchange sites from ISPs who use proxy servers. To avoid this problem we are currently running with "RobotLimit 0". A full explanation of the problem and what I believe is the cause can be found at http://www.icdevgroup.org/pipermail/interchange-users/2004-October/041215.html Here is a snippet: ############ The reason for this is that the check to see whether the addr_ctr file should be expired is only made if RobotLimit has been exceeded. And then, the addr_ctr file is only deleted if the modify date is older than a day (the default for MV_ROBOT_EXPIRE). So, here is the problem: any IP address that is typically allocated more than 1 session id in a 24 hr period will never get its addr_ctr file expired. i.e. There needs to be a full 24 hr period without access from the same IP address before the addr_ctr file will be deleted thus re-allowing access from that IP address. For large ISPs using a relatively small number of proxy servers this may never happen, and so access from their proxy servers is permanently blocked. ############# I know very little Perl so I am not right person to fix the code, but I will be happy to contribute to any discussion on possible solutions. Thanks _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.