On Oct 18, 2:18 am, TomStardust <[email protected]> wrote: > I've found the problem: I thought it was caused by the map embedding > on another site, but I was wrong. > I used > > &key=... > > to build the url. Now I've fixed it with > > &key=... > > and it works fine. > Now that I've discovered the problem, I think using an iframe on > another site is not causing any trouble, is it?
I can think of no case where someone linking to a map on your domain in an iframe on their domain would cause a problem for your domain. -- Larry > > I'm sorry for the trouble, thanks very much for your help. > > On 18 Ott, 10:57, Mike Williams <[email protected]> wrote: > > > What's changed is that the key and sensor parameters are now validated > > for HTTP requests. Until a few days ago, the validation was being > > skipped. > > > Other people whose HTTP geocoding suddenly started getting 610 errors > > this week have found that their PHP code had been sending incorrect key > > or sensor parameters. > > > -- > > Mike Williamshttp://econym.org.uk/gmap --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
