Hi Andrew,
 We have dev and qa environments of the same code and it works on both
(same DB, same code, just different keys for different urls)
 I sniffed the traffic for "http://maps.google.com/maps/geo"; requests
and the response I get returns 620 code.
 The element "mapLocator" does not show up if no results are returned.
(that is an easy patch I can do but I hardly believe that it will fix
the 620 code issue).
 I found some people are talking about adding a "X-Forward-For" header
with an IP of the client(?!) I'm going to try this patch to see if the
problem get's fixed. I'm a little unclear on the header solution from
the posts. I'll try doing that header with the server IP and then the
client IP. If i understood the solution correctly then you should use
clients IP.
 Let me know if you know anything about the "X-Forward-For" header
solution. I'd like to hear more details on how it may help/solver the
problem and why.
Best,

On Jun 8, 11:30 am, Andrew Leach <[email protected]>
wrote:
> On Jun 8, 4:33 pm, CORT <[email protected]> wrote:
>
> >http://www.cort.com/furniture/locator?city=moscow&cityRange=25
>
> > We've been using the API for months now and now all of the sudden we
> > are getting 620 on any queries we send to Google. It started happening
> > sometime today and based on reports we have we've only seen a little
> > under 2,000 requests that happened on the site (way under 15,000/24
> > hrs from the document)
>
> Are you sure it's a 620? I can't find any evidence of geocoding
> activity.
>
> In fact I can't find your element called "mapLocator" either. I think
> things are failing because the API can't actually start.
>
> Andrew
--~--~---------~--~----~------------~-------~--~----~
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=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to