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.
On Aug 30, 8:12 am, Mike <[email protected]> wrote: > I am using HTTP request from the server side of a Java GAE > application. What is the proper key to use? http://appspot.cometc. > do not work... > > Thanks, > > Mike > > On Jul 30, 12:54 am, "pamela (Google Employee)" <[email protected]> > wrote: > > > > > Note: If you are only using GClientGeocoder or ClientGeocoder from the > > JS/Flash APIs, then this message is not relevant to you. This message > > applies only to users of the HTTP Geocoder documented > > here:http://code.google.com/apis/maps/documentation/geocoding/ > > > 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. > > > Please post in the forums if you have questions about this change. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
