UST: I'm having the same problem. I'm getting a 403, without ever seeing a 620. My application is designed to throttle an additional 500ms, when I see a 620.
Google, what's up babies? Should I be looking for a 403 or a 620? On Nov 5, 3:59 pm, UST <[email protected]> wrote: > I get403Forbidden error during HTTP Geocoding. > > Response: '403: Forbidden' for url: 'http://maps.google.com/maps/geo? > q=<address>&output=csv&key=<KEY>&sensor=false&oe=utf8&g1=UK' > > From a search at the group's previous posts, I realize that this error > is given when the IP making Geocoding requests is 'blacklisted' by > Google service since the requests are going too fast. There has to be > a delay of 1.725s between every two requests. > > Now, my questions are as follows: > 1) If the API gives403error for this, then what is error code620 > for? > 2) My code puts a delay of 100ms every time it encounters a620 > error. But apparently, I never receive a620error and so there is no > delay introduced. Is there some 'default' delay to be applied? I had > read in a post that the delay between every request was removed. The > only limitation now is 15000 per day. Is my understanding wrong? If > not, then why am I getting403error? I get this error after about > just 15-20 requests. > > Can anyone can shed some light on this problem? > > Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=.
