On Oct 18, 1:10 pm, "pamela (Google Employee)" <[email protected]> wrote: > Update: We have gone forward with this change. If you are doing HTTP > geocoding and receiving errors suddenly, you should check on the > validity and existence of the key parameter that you send in. It > should match the referrer.
But there is no referer for HTTP requests, so there is nothing for a key to validate against. Any abuse is linked to the account in the key, which may be spoofed; so there is no security there either. I'm afraid this seems to be badly thought through (at best); and the implementation is disastrous, especially since the last word on it prior to making the change was "We won't be doing it". As Roberto has indicated, most apps have some sort of lead time between development and implementation. I fail to see the rationale in making the change. What am I missing? 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 -~----------~----~----~----~------~----~------~--~---
