Compare the JS returned when the wrong key is used on a site with that
when the right key is used. The server side check will have added the
new alert and set G_INCOMPAT to true, but it gets added just *after*
the client side check. So if the client side check fails you will see
the existing message. Right now it's only when the client side check
succeeds and server side check fails that you see the new message, and
it's the cases where this should not have happened that we're working
to track down and address.
On Sep 24, 8:00 pm, Mike Williams <[EMAIL PROTECTED]> wrote:
> Wasn't it Thor who wrote:
>
>
>
> >Quick update on this issue.
>
> >The server side keycheck is applied to all requests, not just to those
> >for Enterprise clients.
>
> I don't think so.
>
> On my pages (non-Enterprise) it still runs the client side check:
>
> !GValidateKey("8ce6331c995a94a48edaa95e38716d5c1040a24e")) {
> G_INCOMPAT = true;alert("The Google Maps API key used on this web
> site was registered for a different web site. You can generate
> a new key for this web site athttp://code.google.com/apis/maps/.";);
> return;
>
> }
>
> That's copied directly from the Javascript as it is right now. If I
> upload a page with a wrong key, I get that error message, not the
> "rejected your request" error, so it doesn't look like it's doing both
> tests.
>
> --http://econym.org.uk/gmap
> The Blackpool Community Church Javascript Team
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
