:( I don't even understand "the need for this". What does it mean to "unfairly [use] the shared resources of the system" when there are quotas and (hopefully hopefully please please please) soon the ability to pay for this service rather than rely on Google to provide it for free?
Even if my service only accepts automated requests and does so /constantly/ that should not be an issue. It definitely would not be a problem for any of the competitors of this product (who would happily take more of my money in exchange for my increase in traffic). If this, in fact, isn't a bug, and there is any "legitimate" reason why this code path would ever be called on an App Engine site, this is immediately a deal breaker for me: for my personal projects and for my clients. -J From: Paul Kinlan Sent: Friday, November 14, 2008 11:24 AM To: google-appengine@googlegroups.com Subject: [google-appengine] Re: 403 - sorry.google.com/sorry - your query looks similar to automated requests Hi, The problem I have is that I will have Apis in the future that will be called in ways that will look like bots and without a way of controlling this feature I will have no way to tell my users what will get their service blocked and for how long it will be blocked. I totally understand the need for this and protection it can give us and how it will stop us from unfairly using the shared resources of the system because of malicious actions of users of our sites, but as developers and the people responsible to our users and clients we can't be blind to how this feature works and how we can help them when they get blocked by this feature. Hopefully this is a bug or a glitch, because otherwise it is an example of how a feature has have been introduced without the users (us) knowing. I have lots of experience and frustrations with vendors not change controlling services adequatly. Kind Regards, Paul. 2008/11/14 [EMAIL PROTECTED] <[EMAIL PROTECTED]> As far as I can tell, this just started. Maybe we missed some notice or change in policy? Perhaps someone could point me to the documentation. More suggestions: Definitely my sites require repeated automated queries. One site records weather related data. The other site records process statistics on multiple computers. I could design each input and request to authenticate. However, I'm hoping this is just a bug. Regards, Mike Chirico On Nov 14, 1:14 pm, Adam <[EMAIL PROTECTED]> wrote: > In my case it's the user's browser that seems to be causing this, > after about 20 seconds of browsing on the map. > > Though before today, I'd never seen it, so I'm hoping somethings > changed that can be un-changed... > > A > > On Nov 14, 1:08 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > Yeah. I'm experiencing the same problem. My application records and > > processes weather data - so yes, there is an automated process hitting > > the site. > > > It would be good if, as administrators, we could create a white list > > of IP addresses. > > > Regards, > > > Mike Chirico > > > On Nov 14, 12:32 pm, Adam <[EMAIL PROTECTED]> wrote: > > > > I've started getting redirected here: > > > >http://sorry.google.com/sorry/?continue=http://www.fyood.com/ > > > > My app has a map page, which sends a lot of requests to the site as > > > the map moves, though I haven't seen this problem before. > > > > Any thoughts, or guidelines on # of requests/second from one IP? > > > > Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
