On Jul 30, 2:14 am, Andrew Leach <[email protected]> wrote: > On Jul 30, 5:54 am, "pamela (Google Employee)" <[email protected]> > wrote: > > > Our system currently permits HTTP Geocoder requests without referers to not > > provide a valid key. In the next few weeks, we will be making a change that > > enforces that a > > valid key must be provided along with an HTTP Geocoder request. Please > > ensure that your HTTP Geocoding requests pass a valid key. > > This may raise an issue with making keys public. So far a key will > only work on the domain it was registered for and isn't needed for > HTTP requests, so it doesn't matter much if it was publicised. If a > key is required but can't be verified against a referer, any key will > do and there is scope for misuse of other people's keys. > > It would be really helpful if subdomains of google.com were > whitelisted and didn't require a key: this would enable HTTP geocode > links without a key to be posted in the Group for example and they > would work in the web interface at least. Email recipients could add > one of their own keys to the request without publishing it.
But all keys are public now. Just go to any web page that contains a google map, the key will be there for the taking. -- Larry > > 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 -~----------~----~----~----~------~----~------~--~---
