Re: API Key returning status 610 when geocoding

I don't have a complaint that it's case sensitive, the mistake was
mine. My code hadn't change since I originally wrote it, and twice
this week I've experienced the 610 error, but it worked inbetween.
It's an easy mistake to make when typing the url in.

On Oct 16, 9:47 am, Andrew Leach <andrew.leac...@googlemail.com>
wrote:
> On Oct 16, 2:36 pm, Terry <develo...@hypersonicscream.com> wrote:
>
>
>
> > See the difference? That's right, the capital letter for Key. I
> > changed it again, it broken again. Changed it to lower case and there
> > it was working.
>
> So it works as documented, and doesn't work if you do something
> different. The reason that Key= used to work is that it wasn't checked
> at all. Now it is, and the server expects a parameter called "key" not
> "Key".
>
> Only Microsoft systems are not case-sensitive; everything else is.
> [The exception is that DNS is documented as being not case-sensitive]
>
> However, I had thought that Pamela had said that HTTP geocoding
> wouldn't require keys; it had been proposed and then dropped. Because
> the Group search is U/S I can't find the thread though.
>
> 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 google-maps-api@googlegroups.com
To unsubscribe from this group, send email to google-maps-api+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en
-~----------~----~----~----~------~----~------~--~---