IP blocked #2565
Comments
Author: twain Hi Onno, I've removed the block - my apologies for using such a drastic method but there was no user agent to identify the application to allow me to contact you. It was put in place because of the number of requests a second and because of the number of duplicate requests - if you could maybe implement some form of caching? With caching the load should be no problem. |
Author: twain [ query information removed ] |
Author: onno.hensgen[at]cas.de Thanks for unblocking our IP and your advice. I'm going to implement a cache. Could you please remove the query addresses from your post or make them illegible. |
Author: twain Replying to [comment:3 onno.hensgen[at]cas.de]:
It doesn't seem to be possible to remove info from a ticket (I've checked with the ops too and they can't either). But once it's closed it's unlikely that anyone will ever look at it again... |
Author: tom[at]compton.nu I've managed to edits the comments directly in the database to remove the query details. |
Author: onno.hensgen[at]cas.de Thanks a lot for your efforts! My superior wasn't happy to see his private address in the web (which i unfortunately used for testing). |
Reporter: onno.hensgen[at]cas.de
[Submitted to the original trac issue database at 2.57pm, Tuesday, 22nd December 2009]
Our IP (213.144.5.2) has been blocked. I'm working for a research project (www.cruise-projekt.de) and used your service for that purpose. I have been using threads for multiple requests and now noticed that I shouldn't do that. I would appreciate if you could unblock our IP again and I won't be using threads again. We use your service only for testing and presentation purposes, so there won't be a constant heavy use in the future.
In our presentation, we geocode a block of addresses (aprox. 30 addresses), but we are doing this very infrequently and if this will ever become part of a real application, we will host our own server for geocoding.
I apologize for the abuse of your service and would be happy to be able to use it again!
With kind regards,
Onno Hensgen
The text was updated successfully, but these errors were encountered: