I'm thinking the throttle approach would be good in the front end. It should
happen once per IP address (essentially), so this huge number of hits could
be decreased dramatically.

Captcha is an idea. It would certainly take care of the bot issue, but I'd
have to consider the intrusiveness. I may also ask for something like that
farther on in the process, so a casual browser wouldn't be affected, while a
buying customer would...but then it would be worth it to them (hopefully).

Thanks...

On Tue, Sep 21, 2010 at 2:05 PM, Thorbjoern Ravn Andersen
<ravn@xxxxxxxxxx>wrote:

Den 21/09/10 17.39, Michael Ryan skrev:
I have a geocoding application where I take an incoming IP address and
determine the metro code. I'm getting hit with tons (seems like tons) of
bots. What's a good way of identifying bots? If I can identify them, I
can
not perform the geocode function.
Throttle the results. Every IP-address can max resolve X codes pr
minute. If you keep getting many increase the response time further.

--
Thorbjørn Ravn Andersen "...plus... Tubular Bells!"

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.