Thanks, Mark, looking forward to the example. You should be able to geocode fine from a proxy, but your limit will be lower then (since it'll be against server IP and not user IP). This article has sample code for it: http://code.google.com/apis/maps/articles/phpsqlgeocode.html
- pamela On Fri, Apr 10, 2009 at 3:32 AM, OldMster <[email protected]> wrote: > > pamela, > Please ignore the link I sent earlier. To meet deadlines, we've > switched the geocode to another service. I will create a smaller, > sample geocode example and send you that link. I'll be able to send > you the project source for the simple example as well. > Mark > > > On Apr 9, 11:52 am, OldMster <[email protected]> wrote: >> pamela, >> I sent you a link privately, the SWF requires a login and I didn't >> want to post that publicly. >> >> Mark >> >> On Apr 8, 2:59 pm, pamela fox <[email protected]> wrote: >> >> > Hi OldMster- >> > Can you post a link to the SWF that shows the issue? >> >> > - pamela >> >> > On Thu, Apr 9, 2009 at 4:30 AM, OldMster <[email protected]> wrote: >> >> > > Any update on this? It really has us blocked on a critical project. >> > > I have tried using thehttp://maps.google.com/maps/geocallto get >> > > around it, but since there isn't a crossdomain policy file on the >> > > google maps server, this fails. I tried setting up a PHP proxy using >> > > curl on our server to get around that, but I get a bad or illegal >> > > request error from the google server. If I copy the url used in the >> > > curl request from the server to a browser, the address geocode comes >> > > up fine. I'm pretty much stumped at this point. >> >> > > On Apr 7, 4:41 pm, OldMster <[email protected]> wrote: >> > > > We have an odd problem with the ClientGeocoder.geocode method. When >> > > > the SWF is loaded from an https: domain, the geocode call always fails >> > > > with status '500'. When watching the network traffic with firebug, >> > > > the call out to the maps.googleapi.com is going with a bad 'url' >> > > > parameter: (below is what is show in Firebug) >> >> > > > urlhttp://https://qo4dev.......... (removed for security) >> >> > > > it has both http:// and https:// on the url - not valid. >> >> > > > When run in debugging mode, the geocode method works, but i suspect it >> > > > is bypassing something when loaded from a local drive, much like the >> > > > key checking is less restrictive. >> >> > > > The other calls we are using from the https: domain work fine, but I >> > > > also don't see the url parameter in them when watching the traffic in >> > > > Firebug. Is this just a bug, or are we doing someting wrong? (v1.94 >> > > > of the google api for Flash) > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" 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-for-flash?hl=en -~----------~----~----~----~------~----~------~--~---
