On production I am getting 610 error returned when using HTTP service
to geocode but the same key works fine for GMAP2 API(display, geocode,
reverseGeocode, etc). Is anyone getting 610 from HTTP all of a sudden?
To test I re-requested a key for domain and copied the example URL(for
geocode google HQ) provided on the key gen page to my production
server. I get 610. I try the same URL from my browser and it works
fine so somehow the key checking must be bypassed when request does
not come from server. I've also mucked up the key for GMAP2 and as
expected I then get a 610 for that. Put it back to my correct key and
GMAP2 works fine but not HTTP service.
Everything(both GMAP2 and HTTP service) works great on local dev
enviornment.
I've not provided link because the problem seems server side and only
thing to see is json response which is below:
{ "name": "1600 Amphitheatre Parkway, Mountain View, CA", "Status":
{ "code": 610, "request": "geocode" } }
Any guidance would be greatly appreciated. Oh yea, I can't image it's
a rate or aggregate limit issue as I've not made more than maybe 100
or so requests in last 24 hours. Plus the GMAP2 keeps on running like
a champ.
thx!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
